Coverage for physical random access channel and repetition of csi report on pusch for coverage enhancement

ABSTRACT

Various embodiments herein provide techniques for improving coverage for a physical random access channel (PRACH). Additionally, embodiments provide techniques for repetition of a channel state information (CSI) report on a physical uplink shared channel (PUSCH) for coverage enhancement. Other embodiments may be described and claimed.

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional PatentApplication No. 63/092,395, which was filed Oct. 15, 2020; U.S.Provisional Patent Application No. 63/092,356, which was filed Oct. 15,2020; the disclosures of which are hereby incorporated by reference.

FIELD

Various embodiments generally may relate to the field of wirelesscommunications. For example, some embodiments may relate to improvingcoverage for a physical random access channel and/or repetition of achannel state information (CSI) report on a physical uplink sharedchannel (PUSCH) for coverage enhancement.

BACKGROUND

Mobile communication has evolved significantly from early voice systemsto today's highly sophisticated integrated communication platform. Thenext generation wireless communication system, 5G, or new radio (NR)will provide access to information and sharing of data anywhere, anytimeby various users and applications. NR is expected to be a unifiednetwork/system that target to meet vastly different and sometimeconflicting performance dimensions and services. Such diversemulti-dimensional requirements are driven by different services andapplications. In general, NR will evolve based on 3GPP Long TermEvolution (LTE)-Advanced with additional potential new Radio AccessTechnologies (RATs) to enrich people lives with better, simple andseamless wireless connectivity solutions. NR will enable everythingconnected by wireless and deliver fast, rich contents and services.

For cellular system, coverage is an important factor for successfuloperation. Compared to LTE, NR can be deployed at relatively highercarrier frequency in frequency range 1 (FR1), e.g., at 3.5 GHz. In thiscase, coverage loss is expected due to larger path-loss, which makes itmore challenging to maintain an adequate quality of service. Typically,uplink coverage is the bottleneck for system operation considering thelow transmit power at the user equipment (UE) side.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings. To facilitatethis description, like reference numerals designate like structuralelements. Embodiments are illustrated by way of example and not by wayof limitation in the figures of the accompanying drawings.

FIG. 1 illustrates a 4-step random access channel (RACH) procedure forinitial access.

FIG. 2 illustrates one example of physical random access channel (PRACH)repetition window, in accordance with various embodiments.

FIG. 3 illustrates one example of applying same synchronization signalblock (SSB) association with PRACH occasion (RO) during PRACHrepetition, in accordance with various embodiments.

FIG. 4 illustrates one example of applying independent SSB associationwith RO during PRACH repetition, in accordance with various embodiments.

FIG. 5 illustrates one example of PRACH resource partitioning for PRACHrepetition and legacy RACH procedure, in accordance with variousembodiments.

FIG. 6 illustrates one example of PRACH resource partitioning for PRACHrepetition and legacy RACH, in accordance with various embodiments.

FIG. 7 illustrates one example of aperiodic channel state information(A-CSI) on physical uplink shared channel (PUSCH) with repetition.

FIG. 8 illustrates one example of repeated A-CSI on PUSCH repetitiontype A, in accordance with various embodiments.

FIG. 9 illustrates one example of carrying A-CSI report on each nominalrepetition when A-CSI report is transmitted on PUSCH with no transportblock, in accordance with various embodiments.

FIG. 10 illustrates one example of carrying A-CSI report on each nominalrepetition when A-CSI report is transmitted on PUSCH with transportblock, in accordance with various embodiments.

FIG. 11 illustrates one example of carrying A-CSI report on each actualrepetition when A-CSI report is transmitted on PUSCH with no transportblock, in accordance with various embodiments.

FIG. 12 illustrates one example of repeating part of symbols fromnominal repetition from the first actual PUCCH repetition, in accordancewith various embodiments.

FIG. 13 schematically illustrates a wireless network in accordance withvarious embodiments.

FIG. 14 schematically illustrates components of a wireless network inaccordance with various embodiments.

FIG. 15 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein.

FIGS. 16-19 illustrate processes to practice various embodiments herein.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.The same reference numbers may be used in different drawings to identifythe same or similar elements. In the following description, for purposesof explanation and not limitation, specific details are set forth suchas particular structures, architectures, interfaces, techniques, etc. inorder to provide a thorough understanding of the various aspects ofvarious embodiments. However, it will be apparent to those skilled inthe art having the benefit of the present disclosure that the variousaspects of the various embodiments may be practiced in other examplesthat depart from these specific details. In certain instances,descriptions of well-known devices, circuits, and methods are omitted soas not to obscure the description of the various embodiments withunnecessary detail. For the purposes of the present document, thephrases “A or B” and “A/B” mean (A), (B), or (A and B).

Various embodiments herein provide techniques for improving coverage fora physical random access channel (PRACH). Additionally, embodimentsprovide techniques for repetition of a channel state information (CSI)report on a physical uplink shared channel (PUSCH) for coverageenhancement.

Improving Coverage for Physical Random Access Channel

In NR Rel-15, a 4-step procedure was defined. FIG. 1 illustrates the4-step random access channel (RACH) procedure for initial access. In thefirst step, UE transmits physical random access channel (PRACH) in theuplink by randomly selecting one preamble signature, which would allowgNB to estimate the delay between gNB and UE for subsequent UL timingadjustment. Subsequently, in the second step, gNB feedbacks the randomaccess response (RAR) which carries timing advanced (TA) commandinformation and uplink grant for the uplink transmission in the thirdstep. The UE expects to receive the RAR within a time window, of whichthe start and end are configured by the gNB via system information block(SIB).

As defined in NR Rel-15, number of repetitions is 2 and 4 for PRACHformat 1 and 2, respectively, which can help in improving the coveragefor long PRACH format. However, for short PRACH format, repetition isnot defined. In order to improve the coverage for PRACH, especiallyshort PRACH format, certain mechanisms may need to be defined.

Embodiments herein provide mechanisms for improving coverage for PRACH(e.g., for NR).

In one embodiment, starting position of PRACH occasion and number ofPRACH repetitions may be configured by higher layers via minimum systeminformation (MSI), remaining minimum system information (RMSI), othersystem information (OSI) or dedicated radio resource control (RRC)signalling. Note that the starting position of PRACH occasion may bedefined in symbol, slot or frame level.

In another option, PRACH repetition window may be configured by higherlayers via MSI, RMSI (SIB1), OSI or RRC signalling. The PRACH repetitionwindow may be aligned with the association period or association patternperiod for mapping SSB indexes to PRACH occasions.

Note that PRACH repetition window may be configured as slot or symbol orframe offset and periodicity. For FR2, reference slot offset may be usedfor PRACH repetition window configuration. Additionally, the number ofrepetitions for PRACH transmission may be separately configured. In thiscase, PRACH repetition window, or parameter PrachRepetiotionWindow canbe defined as the time interval between first and last repetition forPRACH transmission.

FIG. 2 illustrates one example of PRACH repetition window. In theexample, 4 PRACH occasions (RO) can be configured for PRACH repetition.

In another embodiment, for physical downlink control channel (PDCCH)order PRACH transmission, the number of repetitions for PRACHtransmission may be configured by RRC signalling or dynamicallyindicated in the DCI or a combination thereof.

In accordance with various embodiments, the following text in Section7.3.1.2.1 in TS38.212 V16.3.0 may be updated as shown in underline.

If the CRC of the DCI format 1_0 is scrambled by C-RNTI and the“Frequency domain resource assignment” field are of all ones, the DCIformat 1_0 is for random access procedure initiated by a PDCCH order,with all remaining fields set as follows:

-   -   Random Access Preamble index—6 bits according to        ra-PreambleIndex in Clause 5.1.2 of [8, TS38.321]    -   UL/SUL indicator—1 bit. If the value of the “Random Access        Preamble index” is not all zeros and if the UE is configured        with supplementaryUplink in ServingCellConfig in the cell, this        field indicates which UL carrier in the cell to transmit the        PRACH according to Table 7.3.1.1.1-1; otherwise, this field is        reserved    -   SS/PBCH index—6 bits. If the value of the “Random Access        Preamble index” is not all zeros, this field indicates the        SS/PBCH that shall be used to determine the RACH occasion for        the PRACH transmission; otherwise, this field is reserved.    -   PRACH Mask index—4 bits. If the value of the “Random Access        Preamble index” is not all zeros, this field indicates the RACH        occasion associated with the SS/PBCH indicated by “SS/PBCH        index” for the PRACH transmission, according to Clause 5.1.1 of        [8, TS38.321]; otherwise, this field is reserved    -   Number of repetitions for PRACH—2 bits    -   Reserved bits—10 bits for operation in a cell with shared        spectrum channel access; otherwise 8 bits.

In another embodiment, during the PRACH repetition window, same ordifferent Tx beams may be applied for the transmission of PRACH duringrepetitions. Further, whether same or different Tx beams can be appliedfor the transmission of PRACH preamble during repetitions can beconfigured by higher layers via MSI, RMSI (SIB1), OSI or RRC signalling.

Note that during PRACH repetition, if multiple PRACH occasions withPRACH repetition window associated with same synchronization signalblock (SSB) index are multiplexed in a frequency division multiplexing(FDM) manner, UE may only transmit the PRACH preamble in the PRACHoccasion (RO) with lowest index or randomly select one RO fortransmission of PRACH preamble. Further, UE would continue to transmitthe PRACH preamble in the ROs which are multiplexed in a time divisionmultiplexing (TDM) manner with the first RO used for the first PRACHtransmission.

In one option, same Tx beam is applied for the transmission of PRACHpreamble during repetitions. In this case, UE shall associate a same SSBduring repetition. Further, the transmit power or path-loss or referencesignal received power is determined in accordance with the selected SSBindex associated with the PRACH transmission. In other word, sametransmit power is applied for the transmission of PRACH preamble duringrepetition.

Note that during the repetition, UE may select a same PRACH preambleindex during repetition.

FIG. 3 illustrates one example of applying same SSB association with ROduring PRACH repetition. In the example, one SSB index is associatedwith 4 ROs which are multiplexed in an TDM manner. In this case, UE canapply same Tx beam for the PRACH transmission during repetition.

In another option, different Tx beams can be employed for thetransmission of PRACH preamble during repetitions. In this case,different SSB indexes may be associated with different ROs for PRACHtransmission. Further, the transmit power or path-loss or referencesignal received power is determined in accordance with the selected SSBindex associated with different ROs for PRACH repetitions. In otherword, different transmit powers may be applied for the transmission ofPRACH preamble during repetition.

Note that for this case, UE may randomly select PRACH preamble indexduring repetition. Alternatively, UE may select the PRACH preamble indexwhich is same in relative to the staring PRACH preamble index associatedwith different SSB indexes.

FIG. 4 illustrates one example of applying independent SSB associationwith RO during PRACH repetition. In the example, separate SSB indexesare associated with different ROs during PRACH repetition, whichindicates that different Tx beams are applied for the PRACH repetition.

In another embodiment, when UE attempts to monitor random accessresponse (RAR) during a RAR window, the window starts at the firstsymbol of the earliest CORESET the UE is configured to receive PDCCH forType1-PDCCH common search space (CSS) set, that is at least one symbol,after the last symbol of the PRACH occasion corresponding to the lastPRACH transmission.

In accordance with various embodiments, the following text in Section8.2 in TS38.213 V16.3.0 may be updated as indicated in underline:

-   -   In response to a PRACH transmission, a UE attempts to detect a        DCI format 1_0 with CRC scrambled by a corresponding RA-RNTI        during a window controlled by higher layers [11, TS 38.321]. The        window starts at the first symbol of the earliest CORESET the UE        is configured to receive PDCCH for Type1-PDCCH CSS set, as        defined in Clause 10.1, that is at least one symbol, after the        last symbol of the PRACH occasion corresponding to the last        PRACH transmission, where the symbol duration corresponds to the        SCS for Type1-PDCCH CSS set as defined in Clause 10.1. The        length of the window in number of slots, based on the SCS for        Type1-PDCCH CSS set, is provided by ra-ResponseWindow.

In another embodiment, separate PRACH occasions can be configured forPRACH repetition from legacy 4-step and/or 2-step RACH, respectively. Inthis case, separate parameters for SSB to RO association can beconfigured for PRACH with repetition. If not configured, theconfiguration from legacy 4-step RACH and/or 2-step RACH can be reused.

In another embodiment, shared PRACH occasions, but different PRACHpreambles may be configured for PRACH repetition from legacy 4-stepand/or 2-step RACH, respectively.

For example, 64 preambles may be defined for a PRACH occasion (RO).Further, total number of preambles for contention based random access(CBRA) and contention free random access (CFRA) may be configured bytotalNumberOfRA-Preambles, which is further divided into N sets. Eachset of PRACH preambles is associated with one synchronization signalblock (SSB). Within each set of PRACH preambles associated with sameSSB, 4-step CBRA RACH preambles are first mapped, and followed by CBRA2-step RACH preambles. The remaining preambles may be allocated forCFRA.

When PRACH repetition is configured using 4-step RACH, PRACH preamblesfor PRACH repetition may be allocated as a part of consecutive preamblesfor CFRA. In particular, within the set of preambles associated with asame SSB, PRACH preamble for PRACH repetition is allocated after CBRA2-step RACH.

FIG. 5 illustrates one example of PRACH resource partitioning for PRACHrepetition and legacy RACH procedure. In the example, 2 SSBs areassociated with one RO. In addition, preambles with index 0-23 areassociated with SSB #0 and preambles with index 24-47 are associatedwith SSB #1. Further, within the preamble associated with a same SSB,PRACH preamble for PRACH repetition is allocated after CBRA 2-step RACH.

In another embodiment, shared PRACH occasions, but different PRACHpreambles can be configured for PRACH repetition from legacy 4-stepand/or 2-step RACH, respectively. In this option, PRACH repetition for4-step RACH is allocated within the preambles for legacy CBRA 4-stepRACH.

FIG. 6 illustrates one example of PRACH resource partitioning for PRACHrepetition and legacy RACH. In the example, 2 SSBs are associated withone RO. In addition, preambles with index 0-23 are associated with SSB#0 and preambles with index 24-47 are associated with SSB #1 for legacy4-step RACH and 2-step RACH. Further, within each set of preamblesassociated with an SSB, preambles for PRACH repetition for 4-step areallocated within preambles for CBRA 4-step RACH.

In another embodiment, when measured Reference Signal Receive Power(RSRP) is less than or equal to a threshold which is configured byhigher layers via MSI, RMSI (SIB1), OSI or RRC signalling, UE may employPRACH repetition during PRACH repetition window. Otherwise, UE may notuse PRACH repetition.

Alternatively, when path-loss is greater than or equal to a thresholdwhich is configured by higher layers via MSI, RMSI (SIB1), OSI or RRCsignalling, UE may employ PRACH repetition during PRACH repetitionwindow. Otherwise, UE may not use PRACH repetition.

As a further extension, more than one repetition levels may beconfigured, which corresponds to different threshold, which can beconfigured by higher layers via MSI, RMSI (SIB1), OSI or RRC signaling.

In another embodiment of the disclosure, PRACH repetition may also applyfor contention free random access (CFRA) procedure. In this case,dedicated PRACH preamble for PRACH repetition, and PRACH repetitionwindow (which may include starting position and number of repetitions orduration of PRACH repetitions) may be configured by dedicated RRCsignalling.

Repetition of CSI Report on PUSCH for Coverage Enhancement

For NR, dynamic grant and configured grant based physical uplink sharedchannel (PUSCH) transmission are supported. For dynamic grant PUSCHtransmission, PUSCH is scheduled by DCI format 0_0, 0_1 or 0_2. Further,two types of configured grant PUSCH transmission are specified. Inparticular, for Type 1 configured grant PUSCH transmission, UL datatransmission is only based on radio resource control (RRC)(re)configuration without any layer 1 (L1) signaling. In particular,semi-static resource may be configured for one UE, which includes timeand frequency resource, modulation and coding scheme, reference signal,etc. For Type 2 configured grant PUSCH transmission, UL datatransmission is based on both RRC configuration and L1 signaling toactivate/deactivate UL data transmission.

Note that uplink control information (UCI) can be carried by physicaluplink control channel (PUCCH) or PUSCH. In particular, UCI may includescheduling request (SR), hybrid automatic repeat request-acknowledgement(HARQ-ACK) feedback, channel state information (CSI) report, e.g.,channel quality indicator (CQI), pre-coding matrix indicator (PMI), CSIresource indicator (CRI) and rank indicator (RI) and/or beam relatedinformation (e.g., L1-RSRP (layer 1-reference signal received power)).

In NR, if PUSCH slot aggregation is enabled, aperiodic CSI (A-CSI) ismultiplexed only in the PUSCH in the first slot. Further, A-CSI reporttriggered by DCI on PUSCH repetition Type B without UL-SCH is carried onthe first nominal repetition with the other nominal repetitionsdiscarded, In addition, CSI report triggered by DCI on PUSCH repetitionType B with UL-SCH is carried on the first actual repetition.

Similarly, PUSCH scheduled by DCI scrambled by SP-CSI-RNTI doesn'tsupport repetition. In other words, semi-persistent CSI (SP-CSI) is notrepeated on PUSCH. In addition, SP-CSI cannot be multiplexed with uplinkdata.

FIG. 7 illustrates one example of A-CSI on PUSCH with repetition. InFIG. 1, A-CSI is only multiplexed with UL-SCH on the first PUSCHrepetition. Note that although PUSCH repetition type A is shown in FIG.1, the same mechanism is applied for PUSCH repetition type B.

The following text in Section 6.1.2.1 in TS38.214 V16.3.0 describes theCSI report on PUSCH repetition type B:

-   -   For PUSCH repetition Type B, when a UE receives a DCI that        schedules aperiodic CSI report(s) or activates semi-persistent        CSI report(s) on PUSCH with no transport block by a CSI request        field on a DCI, the number of nominal repetitions is always        assumed to be 1, regardless of the value of numberofrepetitions.        When the UE is scheduled to transmit a PUSCH repetition Type B        with no transport block and with aperiodic or semi-persistent        CSI report(s) by a CSI request field on a DCI, the first nominal        repetition is expected to be the same as the first actual        repetition. For PUSCH repetition Type B carrying semi-persistent        CSI report(s) without a corresponding PDCCH after being        activated on PUSCH by a CSI request field on a DCI, if the first        nominal repetition is not the same as the first actual        repetition, the first nominal repetition is omitted; otherwise,        the first nominal repetition is omitted according to the        conditions in Clause 11.1 of [6, TS38.213].    -   For PUSCH repetition Type B, when a UE is scheduled to transmit        a transport block and aperiodic CSI report(s) on PUSCH by a CSI        request field on a DCI, the CSI report(s) is multiplexed only on        the first actual repetition. The UE does not expect that the        first actual repetition has a single symbol duration.

As mentioned above, given that CSI repetition on PUSCH is not supported,this may result in certain coverage issue for CSI report including A-CSIand SP-CSI. Given that CSI carries critical information for properscheduling of downlink transmission, this unreliable CSI report mayaffect performance for physical downlink shared channel (PDSCH) andphysical downlink control channel (PDCCH). In this regard, it isdesirable to enable repetition for CSI report when multiplexed on PUSCHso as to improve the coverage. In this case, certain mechanisms may needto be considered to support repetition of CSI report on PUSCH.

Accordingly, various embodiments herein provide techniques forrepetition of CSI report on PUSCH for coverage enhancement.

In one embodiment, whether repetition of CSI report on PUSCH is enabledcan be configured by higher layers via minimum system information (MR),remaining minimum system information (RMSI), other system information(OSI) or dedicated radio resource control (RRC) signalling. It may beconfigured per DCI format for triggering the A-CSI or as part ofconfiguration for SP-CSI reporting on PUSCH.

For example, when repetition of CSI report on PUSCH is enabled, UE shallrepeat the A-CSI or SP-CSI report on PUSCH.

In another embodiment, number of repetitions for CSI report on PUSCH maybe separately configured or indicated from the number of repetitions forPUSCH. If not configured, the number of repetitions for CSI report onPUSCH can use the one which is configured or indicated for the PUSCHtransmission.

In one option, for PUSCH repetition type A, number of repetitions forCSI report on PUSCH can be separately configured frompusch-AggregationFactor or separately indicated from numberofrepetitionsas part of PUSCH time domain resource assignment (TDRA) indication byDCI formats 0_1 or 0_2. If not configured or indicated separately, itcan reuse pusch-AggregationFactor or as indicated vianumberofrepetitions as part of TDRA indication by DCI formats 0_1 or0_2. Further, the number of repetitions may be configured as part ofCSI-ReportConfig configuration. In another variant, the number ofrepetitions for PUSCH carrying A-CSI may be provided to the UE asscaling factor to the number of repetitions indicated for the PUSCH viapusch-AggregationFactor or via numberofrepetitions as part of TDRAindication.

In another option, for PUSCH repetition type B, number of repetitionsfor CSI report on PUSCH can be separately indicated fromnumberofrepetitions as part of TDRA indication by DCI formats 0_1 or0_2. If not configured, it can reuse numberofrepetitions. Further, thenumber of repetitions may be configured as part of CSI-ReportConfigconfiguration. In another variant, the number of repetitions for PUSCHcarrying A-CSI may be provided to the UE as scaling factor to the numberof repetitions indicated for the PUSCH via pusch-AggregationFactor orvia numberofrepetitions as part of TDRA indication.

Note that when A-CSI is multiplexed on PUSCH with transport block, thenumber of repetitions of A-CSI may follow the number of repetitions forPUSCH. Alternatively, the numbers of repetitions for A-CSI on PUSCH mayfollow the value that may be provided separately frompusch-AggregationFactor or numberofrepetitions as described above,irrespective of whether the A-CSI is multiplexed with UL-SCH in a PUSCHor is transmitted in the PUSCH without any UL-SCH.

When repetition factor for A-CSI is provided separately from PUSCHrepetition factor, a UE may not be expected to be indicated with therepetition factor for A-CSI on PUSCH denoted by N and with a repetitionfactor for PUSCH denoted by M so that N is greater than M, when UL-SCHindicator in DCI format 0_1 or 0_2 is enabled.

In one embodiment, the number of repetitions for SP-CSI on PUSCH isprovided as part of higher layer configuration for CSI-ReportConfig,including indication of Type A or B repetitions for each of thesemi-persistent PUSCH occasions. In another example of the embodiment,the number of repetitions for SP-CSI on PUSCH may be provided to the UEvia a combination of higher layers signaling (e.g., as part ofCSI-ReportConfig) as well as the indication in the DCI format used toactivate the SP-CSI report transmissions. In yet another example of theembodiment, the number of repetitions for SP-CSI on PUSCH may beprovided to the UE via the TDRA field, through the numberofrepetitionscomponent, in the DCI format used to activate the SP-CSI reporttransmissions.

Further, in an example, when provided with SP-CSI on PUSCH configurationusing repetitions, each PUSCH is repeated either following Type A orType B PUSCH repetitions (as indicated or specified), and the UE doesnot expect the periodicity of the PUSCH occasions (corresponding tofirst of a number of repetitions for each PUSCH) to be shorter than theduration corresponding to the configured or indicated number ofrepetitions for each PUSCH.

In another embodiment, the number of repetitions for A-CSI or SP-CSImultiplexed on PUSCH can be configured by a bitmap indicated by higherlayers signaling. The size of a bitmap corresponds to the number ofrepetitions for PUSCH, and the bit value indicates which PUSCHrepetitions include the A-CSI or SP-CSI transmission.

In another embodiment, for PUSCH repetition type A, A-CSI or SP-CSI canbe carried in each PUSCH repetition.

In one option, when A-CSI or SP-CSI is multiplexed on PUSCH with notransport block, the number of repetitions of CSI report on PUSCH mayfollow the number of repetitions which is configured for CSI report onPUSCH. Alternatively, it may follow the number of repetitions which isconfigured for PUSCH transmission.

In another option, when A-CSI is multiplexed on PUSCH with transportblock, the number of repetitions for A-CSI on PUSCH follows the numberof repetitions for PUSCH.

FIG. 8 illustrates one example of repeated A-CSI on PUSCH repetitiontype A. In the example, A-CSI is multiplexed on PUSCH with transportblock or UL-SCH in each slot. In addition, 4 repetitions are applied forA-CSI on PUSCH repetition type A.

In another embodiment, for PUSCH repetition type B, A-CSI or SP-CSIreport may be carried on each nominal repetition.

In one option, for PUSCH repetition Type B, when a UE receives a DCIthat schedules aperiodic CSI report(s) or activates semi-persistent CSIreport(s) on PUSCH with no transport block by a CSI request field on aDCI, UE shall transmit A-CSI or SP-CSI reports on each actual repetitionthat is same as the indicated nominal repetition. When one nominalrepetition is segmented into more than one actual repetition due tocrossing slot boundary, conflict with invalid symbols or semi-static DLsymbols, actual repetitions are not utilized for A-CSI or SP-CSImapping.

FIG. 9 illustrates one example of carrying A-CSI report on each nominalrepetition when A-CSI report is transmitted on PUSCH with no transportblock. In the example, 2^(nd) nominal repetition crosses slot boundaryand is segmented into two actual repetitions. In this case, A-CSI reportis only transmitted on 1^(st) and 3^(rd) nominal repetition. The actualrepetitions in 2^(nd) nominal repetition are dropped.

In another option, for PUSCH repetition Type B, when a UE receives a DCIthat schedules aperiodic CSI report(s) or activates semi-persistent CSIreport(s) on PUSCH with transport block by a CSI request field on a DCI,UE shall transmit A-CSI or SP-CSI reports with transport block on eachactual repetition that is same as the indicated nominal repetition. Inaddition, UE shall transmit only transport block without A-CSI or SP-CSIreport on actual repetition when actual repetition is not same asnominal repetition.

Alternatively, regardless of whether transport block is present onPUSCH, when duration of actual repetition is less than that forindicated nominal repetition, the actual repetition is dropped.

FIG. 10 illustrates one example of carrying A-CSI report on each nominalrepetition when A-CSI report is transmitted on PUSCH with transportblock. In the example, 2nd nominal repetition crosses slot boundary andis segmented into two actual repetitions. In this case, A-CSI report isonly transmitted on 1^(st) and 3^(rd) nominal repetition. Further, onlytransport block or UL-SCH is transmitted in actual PUSCH repetitions in2^(nd) nominal repetition.

In another embodiment, for PUSCH repetition type B, when the number ofbits for CSI report is less than or equal to 11 bits, CSI report iscarried in each actual repetition regardless of whether transport blockis present on PUSCH.

FIG. 11 illustrates one example of carrying A-CSI report on each actualrepetition when A-CSI report is transmitted on PUSCH with no transportblock. The number of bits for A-CSI report is less than or equal to 11.In the example, 2^(nd) nominal repetition crosses slot boundary and issegmented into two actual repetitions. In this case, A-CSI report istransmitted on 1^(st) and 3^(rd) nominal repetition and using the twoactual repetitions in 2^(nd) nominal repetition.

In another embodiment, for PUSCH repetition type B, part of symbols fromnominal repetition may be repeated and transmitted in actual repetition.This may be applied for the cases when transport block is present onPUSCH or when transport block is not present on PUSCH.

As a further extension, a threshold may be defined for the ratio betweenthe length of actual repetition and nominal repetition. Further, thethreshold may be configured by higher layers via MSI, RMSI (SIB1), OSIor RRC signalling. When the ratio between the length of actualrepetition and nominal repetition is less than the threshold, and whenCSI report is multiplexed on PUSCH without transport block, CSI reportis dropped. When CSI report is multiplexed on PUSCH with transportblock, only transport block is transmitted on PUSCH.

When the ratio between the length of actual repetition and nominalrepetition is greater than or equal to the threshold, part of symbolsfrom nominal repetition may be repeated and transmitted in actualrepetition.

FIG. 12 illustrates one example of repeating part of symbols fromnominal repetition from the first actual PUCCH repetition. In theexample, 2^(nd) nominal repetition crosses slot boundary and issegmented into two actual repetitions. In this case, A-CSI report istransmitted on 1^(st) and 3^(rd) nominal repetition. Further, based onthe threshold, part of symbols from 1^(st) nominal repetition arerepeated and transmitted in the 1^(st) actual repetition of the 2ndnominal repetition and 2^(nd) actual repetition of the 2nd nominalrepetition is cancelled.

Additionally, the procedure for selection of different nominal symbolsfor 1^(st) and 2^(nd) actual repetitions of the nominal repetitiondivided by slot boundary can be used. For example, symbols from nominalrepetition are repeated in 1^(st) and 2^(nd) actual repetition based onthe segmentation, respectively.

In another embodiment, for PUSCH repetition type B, CSI report iscarried in each actual repetition regardless of whether transport blockis present on PUSCH.

In one embodiment, when repetition of A-CSI/SP-CSI on PUSCH is enabled,number of resource elements for A-CSI or SP-CSI on PUSCH may bedetermined in accordance with one of the following options:

The total number of REs for PUSCH for determination of the REs forA-CSI/SP-CSI part 1 and part 2 may be calculated from the nominalrepetition length

The total number of REs for PUSCH for determination of the REs forA-CSI/SP-CSI part 1 and part 2 may be calculated from an actualrepetition length

In one option, the first actual repetition length may be used.

In another option, the minimum length among all scheduled actualrepetitions may be used.

In yet another option, the maximum length among all scheduled actualrepetitions may be used.

Systems and Implementations

FIGS. 13-15 illustrate various systems, devices, and components that mayimplement aspects of disclosed embodiments.

FIG. 13 illustrates a network 1300 in accordance with variousembodiments. The network 1300 may operate in a manner consistent with3GPP technical specifications for LTE or 5G/NR systems. However, theexample embodiments are not limited in this regard and the describedembodiments may apply to other networks that benefit from the principlesdescribed herein, such as future 3GPP systems, or the like.

The network 1300 may include a UE 1302, which may include any mobile ornon-mobile computing device designed to communicate with a RAN 1304 viaan over-the-air connection. The UE 1302 may be communicatively coupledwith the RAN 1304 by a Uu interface. The UE 1302 may be, but is notlimited to, a smartphone, tablet computer, wearable computer device,desktop computer, laptop computer, in-vehicle infotainment, in-carentertainment device, instrument cluster, head-up display device,onboard diagnostic device, dashtop mobile equipment, mobile dataterminal, electronic engine management system, electronic/engine controlunit, electronic/engine control module, embedded system, sensor,microcontroller, control module, engine management system, networkedappliance, machine-type communication device, M2M or D2D device, IoTdevice, etc.

In some embodiments, the network 1300 may include a plurality of UEscoupled directly with one another via a sidelink interface. The UEs maybe M2M/D2D devices that communicate using physical sidelink channelssuch as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

In some embodiments, the UE 1302 may additionally communicate with an AP1306 via an over-the-air connection. The AP 1306 may manage a WLANconnection, which may serve to offload some/all network traffic from theRAN 1304. The connection between the UE 1302 and the AP 1306 may beconsistent with any IEEE 802.11 protocol, wherein the AP 1306 could be awireless fidelity (Wi-Fi®) router. In some embodiments, the UE 1302, RAN1304, and AP 1306 may utilize cellular-WLAN aggregation (for example,LWA/LWIP). Cellular-WLAN aggregation may involve the UE 1302 beingconfigured by the RAN 1304 to utilize both cellular radio resources andWLAN resources.

The RAN 1304 may include one or more access nodes, for example, AN 1308.AN 1308 may terminate air-interface protocols for the UE 1302 byproviding access stratum protocols including RRC, PDCP, RLC, MAC, and L1protocols. In this manner, the AN 1308 may enable data/voiceconnectivity between CN 1320 and the UE 1302. In some embodiments, theAN 1308 may be implemented in a discrete device or as one or moresoftware entities running on server computers as part of, for example, avirtual network, which may be referred to as a CRAN or virtual basebandunit pool. The AN 1308 be referred to as a BS, gNB, RAN node, eNB,ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 1308 may be a macrocell basestation or a low power base station for providing femtocells, picocellsor other like cells having smaller coverage areas, smaller usercapacity, or higher bandwidth compared to macrocells.

In embodiments in which the RAN 1304 includes a plurality of ANs, theymay be coupled with one another via an X2 interface (if the RAN 1304 isan LTE RAN) or an Xn interface (if the RAN 1304 is a 5G RAN). The X2/Xninterfaces, which may be separated into control/user plane interfaces insome embodiments, may allow the ANs to communicate information relatedto handovers, data/context transfers, mobility, load management,interference coordination, etc.

The ANs of the RAN 1304 may each manage one or more cells, cell groups,component carriers, etc. to provide the UE 1302 with an air interfacefor network access. The UE 1302 may be simultaneously connected with aplurality of cells provided by the same or different ANs of the RAN1304. For example, the UE 1302 and RAN 1304 may use carrier aggregationto allow the UE 1302 to connect with a plurality of component carriers,each corresponding to a Pcell or Scell. In dual connectivity scenarios,a first AN may be a master node that provides an MCG and a second AN maybe secondary node that provides an SCG. The first/second ANs may be anycombination of eNB, gNB, ng-eNB, etc.

The RAN 1304 may provide the air interface over a licensed spectrum oran unlicensed spectrum. To operate in the unlicensed spectrum, the nodesmay use LAA, eLAA, and/or feLAA mechanisms based on CA technology withPCells/Scells. Prior to accessing the unlicensed spectrum, the nodes mayperform medium/carrier-sensing operations based on, for example, alisten-before-talk (LBT) protocol.

In V2X scenarios the UE 1302 or AN 1308 may be or act as a RSU, whichmay refer to any transportation infrastructure entity used for V2Xcommunications. An RSU may be implemented in or by a suitable AN or astationary (or relatively stationary) UE. An RSU implemented in or by: aUE may be referred to as a “UE-type RSU”; an eNB may be referred to asan “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and thelike. In one example, an RSU is a computing device coupled with radiofrequency circuitry located on a roadside that provides connectivitysupport to passing vehicle UEs. The RSU may also include internal datastorage circuitry to store intersection map geometry, trafficstatistics, media, as well as applications/software to sense and controlongoing vehicular and pedestrian traffic. The RSU may provide very lowlatency communications required for high speed events, such as crashavoidance, traffic warnings, and the like. Additionally oralternatively, the RSU may provide other cellular/WLAN communicationsservices. The components of the RSU may be packaged in a weatherproofenclosure suitable for outdoor installation, and may include a networkinterface controller to provide a wired connection (e.g., Ethernet) to atraffic signal controller or a backhaul network.

In some embodiments, the RAN 1304 may be an LTE RAN 1310 with eNBs, forexample, eNB 1312. The LTE RAN 1310 may provide an LTE air interfacewith the following characteristics: SCS of 15 kHz; CP-OFDM waveform forDL and SC-FDMA waveform for UL; turbo codes for data and TBCC forcontrol; etc. The LTE air interface may rely on CSI-RS for CSIacquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCHdemodulation; and CRS for cell search and initial acquisition, channelquality measurements, and channel estimation for coherentdemodulation/detection at the UE. The LTE air interface may operating onsub-6 GHz bands.

In some embodiments, the RAN 1304 may be an NG-RAN 1314 with gNBs, forexample, gNB 1316, or ng-eNBs, for example, ng-eNB 1318. The gNB 1316may connect with 5G-enabled UEs using a 5G NR interface. The gNB 1316may connect with a 5G core through an NG interface, which may include anN2 interface or an N3 interface. The ng-eNB 1318 may also connect withthe 5G core through an NG interface, but may connect with a UE via anLTE air interface. The gNB 1316 and the ng-eNB 1318 may connect witheach other over an Xn interface.

In some embodiments, the NG interface may be split into two parts, an NGuser plane (NG-U) interface, which carries traffic data between thenodes of the NG-RAN 1314 and a UPF 1348 (e.g., N3 interface), and an NGcontrol plane (NG-C) interface, which is a signaling interface betweenthe nodes of the NG-RAN 1314 and an AMF 1344 (e.g., N2 interface).

The NG-RAN 1314 may provide a 5G-NR air interface with the followingcharacteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDMfor UL; polar, repetition, simplex, and Reed-Muller codes for controland LDPC for data. The 5G-NR air interface may rely on CSI-RS,PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR airinterface may not use a CRS, but may use PBCH DMRS for PBCHdemodulation; PTRS for phase tracking for PDSCH; and tracking referencesignal for time tracking. The 5G-NR air interface may operating on FR1bands that include sub-6 GHz bands or FR2 bands that include bands from24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB thatis an area of a downlink resource grid that includes PSS/SSS/PBCH.

In some embodiments, the 5G-NR air interface may utilize BWPs forvarious purposes. For example, BWP can be used for dynamic adaptation ofthe SCS. For example, the UE 1302 can be configured with multiple BWPswhere each BWP configuration has a different SCS. When a BWP change isindicated to the UE 1302, the SCS of the transmission is changed aswell. Another use case example of BWP is related to power saving. Inparticular, multiple BWPs can be configured for the UE 1302 withdifferent amount of frequency resources (for example, PRBs) to supportdata transmission under different traffic loading scenarios. A BWPcontaining a smaller number of PRBs can be used for data transmissionwith small traffic load while allowing power saving at the UE 1302 andin some cases at the gNB 1316. A BWP containing a larger number of PRBscan be used for scenarios with higher traffic load.

The RAN 1304 is communicatively coupled to CN 1320 that includes networkelements to provide various functions to support data andtelecommunications services to customers/subscribers (for example, usersof UE 1302). The components of the CN 1320 may be implemented in onephysical node or separate physical nodes. In some embodiments, NFV maybe utilized to virtualize any or all of the functions provided by thenetwork elements of the CN 1320 onto physical compute/storage resourcesin servers, switches, etc. A logical instantiation of the CN 1320 may bereferred to as a network slice, and a logical instantiation of a portionof the CN 1320 may be referred to as a network sub-slice.

In some embodiments, the CN 1320 may be an LTE CN 1322, which may alsobe referred to as an EPC. The LTE CN 1322 may include MME 1324, SGW1326, SGSN 1328, HSS 1330, PGW 1332, and PCRF 1334 coupled with oneanother over interfaces (or “reference points”) as shown. Functions ofthe elements of the LTE CN 1322 may be briefly introduced as follows.

The MME 1324 may implement mobility management functions to track acurrent location of the UE 1302 to facilitate paging, beareractivation/deactivation, handovers, gateway selection, authentication,etc.

The SGW 1326 may terminate an S1 interface toward the RAN and route datapackets between the RAN and the LTE CN 1322. The SGW 1326 may be a localmobility anchor point for inter-RAN node handovers and also may providean anchor for inter-3GPP mobility. Other responsibilities may includelawful intercept, charging, and some policy enforcement.

The SGSN 1328 may track a location of the UE 1302 and perform securityfunctions and access control. In addition, the SGSN 1328 may performinter-EPC node signaling for mobility between different RAT networks;PDN and S-GW selection as specified by MME 1324; MME selection forhandovers; etc. The S3 reference point between the MME 1324 and the SGSN1328 may enable user and bearer information exchange for inter-3GPPaccess network mobility in idle/active states.

The HSS 1330 may include a database for network users, includingsubscription-related information to support the network entities'handling of communication sessions. The HSS 1330 can provide support forrouting/roaming, authentication, authorization, naming/addressingresolution, location dependencies, etc. An S6a reference point betweenthe HSS 1330 and the MME 1324 may enable transfer of subscription andauthentication data for authenticating/authorizing user access to theLTE CN 1320.

The PGW 1332 may terminate an SGi interface toward a data network (DN)1336 that may include an application/content server 1338. The PGW 1332may route data packets between the LTE CN 1322 and the data network1336. The PGW 1332 may be coupled with the SGW 1326 by an S5 referencepoint to facilitate user plane tunneling and tunnel management. The PGW1332 may further include a node for policy enforcement and charging datacollection (for example, PCEF). Additionally, the SGi reference pointbetween the PGW 1332 and the data network 1336 may be an operatorexternal public, a private PDN, or an intra-operator packet datanetwork, for example, for provision of IMS services. The PGW 1332 may becoupled with a PCRF 1334 via a Gx reference point.

The PCRF 1334 is the policy and charging control element of the LTE CN1322. The PCRF 1334 may be communicatively coupled to the app/contentserver 1338 to determine appropriate QoS and charging parameters forservice flows. The PCRF 1332 may provision associated rules into a PCEF(via Gx reference point) with appropriate TFT and QCI.

In some embodiments, the CN 1320 may be a 5GC 1340. The 5GC 1340 mayinclude an AUSF 1342, AMF 1344, SMF 1346, UPF 1348, NSSF 1350, NEF 1352,NRF 1354, PCF 1356, UDM 1358, and AF 1360 coupled with one another overinterfaces (or “reference points”) as shown. Functions of the elementsof the 5GC 1340 may be briefly introduced as follows.

The AUSF 1342 may store data for authentication of UE 1302 and handleauthentication-related functionality. The AUSF 1342 may facilitate acommon authentication framework for various access types. In addition tocommunicating with other elements of the 5GC 1340 over reference pointsas shown, the AUSF 1342 may exhibit an Nausf service-based interface.

The AMF 1344 may allow other functions of the 5GC 1340 to communicatewith the UE 1302 and the RAN 1304 and to subscribe to notificationsabout mobility events with respect to the UE 1302. The AMF 1344 may beresponsible for registration management (for example, for registering UE1302), connection management, reachability management, mobilitymanagement, lawful interception of AMF-related events, and accessauthentication and authorization. The AMF 1344 may provide transport forSM messages between the UE 1302 and the SMF 1346, and act as atransparent proxy for routing SM messages. AMF 1344 may also providetransport for SMS messages between UE 1302 and an SMSF. AMF 1344 mayinteract with the AUSF 1342 and the UE 1302 to perform various securityanchor and context management functions. Furthermore, AMF 1344 may be atermination point of a RAN CP interface, which may include or be an N2reference point between the RAN 1304 and the AMF 1344; and the AMF 1344may be a termination point of NAS (N1) signaling, and perform NASciphering and integrity protection. AMF 1344 may also support NASsignaling with the UE 1302 over an N3 IWF interface.

The SMF 1346 may be responsible for SM (for example, sessionestablishment, tunnel management between UPF 1348 and AN 1308); UE IPaddress allocation and management (including optional authorization);selection and control of UP function; configuring traffic steering atUPF 1348 to route traffic to proper destination; termination ofinterfaces toward policy control functions; controlling part of policyenforcement, charging, and QoS; lawful intercept (for SM events andinterface to LI system); termination of SM parts of NAS messages;downlink data notification; initiating AN specific SM information, sentvia AMF 1344 over N2 to AN 1308; and determining SSC mode of a session.SM may refer to management of a PDU session, and a PDU session or“session” may refer to a PDU connectivity service that provides orenables the exchange of PDUs between the UE 1302 and the data network1336.

The UPF 1348 may act as an anchor point for intra-RAT and inter-RATmobility, an external PDU session point of interconnect to data network1336, and a branching point to support multi-homed PDU session. The UPF1348 may also perform packet routing and forwarding, perform packetinspection, enforce the user plane part of policy rules, lawfullyintercept packets (UP collection), perform traffic usage reporting,perform QoS handling for a user plane (e.g., packet filtering, gating,UL/DL rate enforcement), perform uplink traffic verification (e.g.,SDF-to-QoS flow mapping), transport level packet marking in the uplinkand downlink, and perform downlink packet buffering and downlink datanotification triggering. UPF 1348 may include an uplink classifier tosupport routing traffic flows to a data network.

The NSSF 1350 may select a set of network slice instances serving the UE1302. The NSSF 1350 may also determine allowed NSSAI and the mapping tothe subscribed S-NSSAIs, if needed. The NSSF 1350 may also determine theAMF set to be used to serve the UE 1302, or a list of candidate AMFsbased on a suitable configuration and possibly by querying the NRF 1354.The selection of a set of network slice instances for the UE 1302 may betriggered by the AMF 1344 with which the UE 1302 is registered byinteracting with the NSSF 1350, which may lead to a change of AMF. TheNSSF 1350 may interact with the AMF 1344 via an N22 reference point; andmay communicate with another NSSF in a visited network via an N31reference point (not shown). Additionally, the NSSF 1350 may exhibit anNnssf service-based interface.

The NEF 1352 may securely expose services and capabilities provided by3GPP network functions for third party, internal exposure/re-exposure,AFs (e.g., AF 1360), edge computing or fog computing systems, etc. Insuch embodiments, the NEF 1352 may authenticate, authorize, or throttlethe AFs. NEF 1352 may also translate information exchanged with the AF1360 and information exchanged with internal network functions. Forexample, the NEF 1352 may translate between an AF-Service-Identifier andan internal 5GC information. NEF 1352 may also receive information fromother NFs based on exposed capabilities of other NFs. This informationmay be stored at the NEF 1352 as structured data, or at a data storageNF using standardized interfaces. The stored information can then bere-exposed by the NEF 1352 to other NFs and AFs, or used for otherpurposes such as analytics. Additionally, the NEF 1352 may exhibit anNnef service-based interface.

The NRF 1354 may support service discovery functions, receive NFdiscovery requests from NF instances, and provide the information of thediscovered NF instances to the NF instances. NRF 1354 also maintainsinformation of available NF instances and their supported services. Asused herein, the terms “instantiate,” “instantiation,” and the like mayrefer to the creation of an instance, and an “instance” may refer to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code. Additionally, the NRF 1354 may exhibit theNnrf service-based interface.

The PCF 1356 may provide policy rules to control plane functions toenforce them, and may also support unified policy framework to governnetwork behavior. The PCF 1356 may also implement a front end to accesssubscription information relevant for policy decisions in a UDR of theUDM 1358. In addition to communicating with functions over referencepoints as shown, the PCF 1356 exhibit an Npcf service-based interface.

The UDM 1358 may handle subscription-related information to support thenetwork entities' handling of communication sessions, and may storesubscription data of UE 1302. For example, subscription data may becommunicated via an N8 reference point between the UDM 1358 and the AMF1344. The UDM 1358 may include two parts, an application front end and aUDR. The UDR may store subscription data and policy data for the UDM1358 and the PCF 1356, and/or structured data for exposure andapplication data (including PFDs for application detection, applicationrequest information for multiple UEs 1302) for the NEF 1352. The Nudrservice-based interface may be exhibited by the UDR 221 to allow the UDM1358, PCF 1356, and NEF 1352 to access a particular set of the storeddata, as well as to read, update (e.g., add, modify), delete, andsubscribe to notification of relevant data changes in the UDR. The UDMmay include a UDM-FE, which is in charge of processing credentials,location management, subscription management and so on. Severaldifferent front ends may serve the same user in different transactions.The UDM-FE accesses subscription information stored in the UDR andperforms authentication credential processing, user identificationhandling, access authorization, registration/mobility management, andsubscription management. In addition to communicating with other NFsover reference points as shown, the UDM 1358 may exhibit the Nudmservice-based interface.

The AF 1360 may provide application influence on traffic routing,provide access to NEF, and interact with the policy framework for policycontrol.

In some embodiments, the 5GC 1340 may enable edge computing by selectingoperator/3rd party services to be geographically close to a point thatthe UE 1302 is attached to the network. This may reduce latency and loadon the network. To provide edge-computing implementations, the 5GC 1340may select a UPF 1348 close to the UE 1302 and execute traffic steeringfrom the UPF 1348 to data network 1336 via the N6 interface. This may bebased on the UE subscription data, UE location, and information providedby the AF 1360. In this way, the AF 1360 may influence UPF (re)selectionand traffic routing. Based on operator deployment, when AF 1360 isconsidered to be a trusted entity, the network operator may permit AF1360 to interact directly with relevant NFs. Additionally, the AF 1360may exhibit an Naf service-based interface.

The data network 1336 may represent various network operator services,Internet access, or third party services that may be provided by one ormore servers including, for example, application/content server 1338.

FIG. 14 schematically illustrates a wireless network 1400 in accordancewith various embodiments. The wireless network 1400 may include a UE1402 in wireless communication with an AN 1404. The UE 1402 and AN 1404may be similar to, and substantially interchangeable with, like-namedcomponents described elsewhere herein.

The UE 1402 may be communicatively coupled with the AN 1404 viaconnection 1406. The connection 1406 is illustrated as an air interfaceto enable communicative coupling, and can be consistent with cellularcommunications protocols such as an LTE protocol or a 5G NR protocoloperating at mmWave or sub-6 GHz frequencies.

The UE 1402 may include a host platform 1408 coupled with a modemplatform 1410. The host platform 1408 may include application processingcircuitry 1412, which may be coupled with protocol processing circuitry1414 of the modem platform 1410. The application processing circuitry1412 may run various applications for the UE 1402 that source/sinkapplication data. The application processing circuitry 1412 may furtherimplement one or more layer operations to transmit/receive applicationdata to/from a data network. These layer operations may includetransport (for example UDP) and Internet (for example, IP) operations

The protocol processing circuitry 1414 may implement one or more oflayer operations to facilitate transmission or reception of data overthe connection 1406. The layer operations implemented by the protocolprocessing circuitry 1414 may include, for example, MAC, RLC, PDCP, RRCand NAS operations.

The modem platform 1410 may further include digital baseband circuitry1416 that may implement one or more layer operations that are “below”layer operations performed by the protocol processing circuitry 1414 ina network protocol stack. These operations may include, for example, PHYoperations including one or more of HARQ-ACK functions,scrambling/descrambling, encoding/decoding, layer mapping/de-mapping,modulation symbol mapping, received symbol/bit metric determination,multi-antenna port precoding/decoding, which may include one or more ofspace-time, space-frequency or spatial coding, reference signalgeneration/detection, preamble sequence generation and/or decoding,synchronization sequence generation/detection, control channel signalblind decoding, and other related functions.

The modem platform 1410 may further include transmit circuitry 1418,receive circuitry 1420, RF circuitry 1422, and RF front end (RFFE) 1424,which may include or connect to one or more antenna panels 1426.Briefly, the transmit circuitry 1418 may include a digital-to-analogconverter, mixer, intermediate frequency (IF) components, etc.; thereceive circuitry 1420 may include an analog-to-digital converter,mixer, IF components, etc.; the RF circuitry 1422 may include alow-noise amplifier, a power amplifier, power tracking components, etc.;RFFE 1424 may include filters (for example, surface/bulk acoustic wavefilters), switches, antenna tuners, beamforming components (for example,phase-array antenna components), etc. The selection and arrangement ofthe components of the transmit circuitry 1418, receive circuitry 1420,RF circuitry 1422, RFFE 1424, and antenna panels 1426 (referredgenerically as “transmit/receive components”) may be specific to detailsof a specific implementation such as, for example, whether communicationis TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In someembodiments, the transmit/receive components may be arranged in multipleparallel transmit/receive chains, may be disposed in the same ordifferent chips/modules, etc.

In some embodiments, the protocol processing circuitry 1414 may includeone or more instances of control circuitry (not shown) to providecontrol functions for the transmit/receive components.

A UE reception may be established by and via the antenna panels 1426,RFFE 1424, RF circuitry 1422, receive circuitry 1420, digital basebandcircuitry 1416, and protocol processing circuitry 1414. In someembodiments, the antenna panels 1426 may receive a transmission from theAN 1404 by receive-beamforming signals received by a plurality ofantennas/antenna elements of the one or more antenna panels 1426.

A UE transmission may be established by and via the protocol processingcircuitry 1414, digital baseband circuitry 1416, transmit circuitry1418, RF circuitry 1422, RFFE 1424, and antenna panels 1426. In someembodiments, the transmit components of the UE 1404 may apply a spatialfilter to the data to be transmitted to form a transmit beam emitted bythe antenna elements of the antenna panels 1426.

Similar to the UE 1402, the AN 1404 may include a host platform 1428coupled with a modem platform 1430. The host platform 1428 may includeapplication processing circuitry 1432 coupled with protocol processingcircuitry 1434 of the modem platform 1430. The modem platform mayfurther include digital baseband circuitry 1436, transmit circuitry1438, receive circuitry 1440, RF circuitry 1442, RFFE circuitry 1444,and antenna panels 1446. The components of the AN 1404 may be similar toand substantially interchangeable with like-named components of the UE1402. In addition to performing data transmission/reception as describedabove, the components of the AN 1408 may perform various logicalfunctions that include, for example, RNC functions such as radio bearermanagement, uplink and downlink dynamic radio resource management, anddata packet scheduling.

FIG. 15 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein. Specifically, FIG. 15 shows a diagrammaticrepresentation of hardware resources 1500 including one or moreprocessors (or processor cores) 1510, one or more memory/storage devices1520, and one or more communication resources 1530, each of which may becommunicatively coupled via a bus 1540 or other interface circuitry. Forembodiments where node virtualization (e.g., NFV) is utilized, ahypervisor 1502 may be executed to provide an execution environment forone or more network slices/sub-slices to utilize the hardware resources1500.

The processors 1510 may include, for example, a processor 1512 and aprocessor 1514. The processors 1510 may be, for example, a centralprocessing unit (CPU), a reduced instruction set computing (RISC)processor, a complex instruction set computing (CISC) processor, agraphics processing unit (GPU), a DSP such as a baseband processor, anASIC, an FPGA, a radio-frequency integrated circuit (RFIC), anotherprocessor (including those discussed herein), or any suitablecombination thereof.

The memory/storage devices 1520 may include main memory, disk storage,or any suitable combination thereof. The memory/storage devices 1520 mayinclude, but are not limited to, any type of volatile, non-volatile, orsemi-volatile memory such as dynamic random access memory (DRAM), staticrandom access memory (SRAM), erasable programmable read-only memory(EPROM), electrically erasable programmable read-only memory (EEPROM),Flash memory, solid-state storage, etc.

The communication resources 1530 may include interconnection or networkinterface controllers, components, or other suitable devices tocommunicate with one or more peripheral devices 1504 or one or moredatabases 1506 or other network elements via a network 1508. Forexample, the communication resources 1530 may include wiredcommunication components (e.g., for coupling via USB, Ethernet, etc.),cellular communication components, NFC components, Bluetooth® (orBluetooth® Low Energy) components, Wi-Fi® components, and othercommunication components.

Instructions 1550 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 1510 to perform any one or more of the methodologiesdiscussed herein. The instructions 1550 may reside, completely orpartially, within at least one of the processors 1510 (e.g., within theprocessor's cache memory), the memory/storage devices 1520, or anysuitable combination thereof. Furthermore, any portion of theinstructions 1550 may be transferred to the hardware resources 1500 fromany combination of the peripheral devices 1504 or the databases 1506.Accordingly, the memory of processors 1510, the memory/storage devices1520, the peripheral devices 1504, and the databases 1506 are examplesof computer-readable and machine-readable media.

Example Procedures

In some embodiments, the electronic device(s), network(s), system(s),chip(s) or component(s), or portions or implementations thereof, ofFIGS. 13-15, or some other figure herein, may be configured to performone or more processes, techniques, or methods as described herein, orportions thereof. One such process is depicted in FIG. 16. Inembodiments, the process may be performed by a UE or a portion thereof.For example, the process may include, at 1602, receiving, from a gNodeB(gNB), configuration information to indicate a repetition window for aPRACH, wherein the repetition window includes a plurality of PRACHoccasions. At 1604, the process may further include encoding a PRACHmessage for transmission with repetition in the respective PRACHoccasions. In some embodiments, the configuration information mayindicate a starting position and/or a number of PRACH repetitions (e.g.,a number of the PRACH occasions) of the repetition window.

FIG. 17 illustrates another process in accordance with variousembodiments. In some embodiments, the process may be performed by a gNBor a portion thereof. At 1702, the process may include encoding, fortransmission to a UE, configuration information to indicate a repetitionwindow for a PRACH, wherein the repetition window includes a pluralityof PRACH occasions. At 1704, the process may further include receiving,from the UE, a PRACH message with repetition in the respective PRACHoccasions. In some embodiments, the configuration information mayindicate a starting position and/or a number of PRACH repetitions (e.g.,a number of the PRACH occasions) of the repetition window.

FIG. 18 illustrates another process in accordance with variousembodiments. In some embodiments, the process of FIG. 18 may beperformed by a UE or a portion thereof. At 1802, the process may includereceiving configuration information to configure repetitions of a CSIreport on a PUSCH, wherein the CSI report includes an A-CSI report or aSP-CSI report. At 1804, the process may further include receiving a DCIto trigger the A-CSI report or activate the SP-CSI report. At 1806, theprocess may further include encoding, for transmission on the PUSCH, theCSI report with repetitions based on the configuration information andthe DCI.

FIG. 19 illustrates another process in accordance with variousembodiments. In some embodiments, the process may be performed by a gNBor a portion thereof. At 1902, the process may include encoding, fortransmission to a UE, configuration information to configure repetitionsof a CSI report on a PUSCH, wherein the CSI report includes an A-CSIreport or a SP-CSI report. At 1804, the process may further includeencoding, for transmission to the UE, a DCI to trigger the A-CSI reportor activate the SP-CSI report. At 1806, the process may further includereceiving, from the UE on the PUSCH, the CSI report with repetitionsbased on the configuration information and the DCI.

For one or more embodiments, at least one of the components set forth inone or more of the preceding figures may be configured to perform one ormore operations, techniques, processes, and/or methods as set forth inthe example section below. For example, the baseband circuitry asdescribed above in connection with one or more of the preceding figuresmay be configured to operate in accordance with one or more of theexamples set forth below. For another example, circuitry associated witha UE, base station, network element, etc. as described above inconnection with one or more of the preceding figures may be configuredto operate in accordance with one or more of the examples set forthbelow in the example section.

Examples

Example A1 may include a method of wireless communication for a fifthgeneration (5G) or new radio (NR) system, the method comprising:receiving, by a UE from a gNodeB (gNB), a physical random access channel(PRACH) repetition window and a number of repetitions for PRACH; andTransmitting, by UE, the PRACH with repetition within the PRACHrepetition window.

Example A2 may include the method of example A1 or some other exampleherein, wherein starting position of PRACH occasion and number of PRACHrepetitions may be configured by higher layers via minimum systeminformation (MR), remaining minimum system information (RMSI), othersystem information (OSI) or dedicated radio resource control (RRC)signalling

Example A3 may include the method of example A1 or some other exampleherein, wherein PRACH repetition window may be configured by higherlayers via MSI, RMSI (SIB1), OSI or RRC signalling, wherein the PRACHrepetition window may be aligned with the association period orassociation pattern period for mapping SSB indexes to PRACH occasions.

Example A4 may include the method of example A1 or some other exampleherein, wherein PRACH repetition window may be configured as slot orsymbol or frame offset and periodicity.

Example A5 may include the method of example A1 or some other exampleherein, wherein for physical downlink control channel (PDCCH) orderPRACH transmission, the number of repetitions for PRACH repetitions maybe configured by RRC signalling or dynamically indicated in the DCI or acombination thereof.

Example A6 may include the method of example A1 or some other exampleherein, wherein during the PRACH repetition window, same or different Txbeams may be applied for the transmission of PRACH during repetitions

Example A7 may include the method of example A1 or some other exampleherein, wherein whether same or different Tx beams can be applied forthe transmission of PRACH preamble during repetitions can be configuredby higher layers via MSI, RMSI (SIB1), OSI or RRC signalling.

Example A8 may include the method of example A1 or some other exampleherein, wherein if multiple PRACH occasions with PRACH repetition windowassociated with same synchronization signal block (SSB) index aremultiplexed in a frequency division multiplexing (FDM) manner, UE mayonly transmit the PRACH preamble in the PRACH occasion (RO) with lowestindex or randomly select one RO for transmission of PRACH preamble.

Example A9 may include the method of example A1 or some other exampleherein, wherein UE shall associate a same SSB during repetition, whereinthe transmit power or path-loss or reference signal received power isdetermined in accordance with the selected SSB index associated with thePRACH transmission

Example A10 may include the method of example A1 or some other exampleherein, wherein different SSB indexes may be associated with differentROs for PRACH transmission, wherein the transmit power or path-loss orreference signal received power is determined in accordance with theselected SSB index associated with different ROs for PRACH repetitions

Example A11 may include the method of example A1 or some other exampleherein, wherein when UE attempts to monitor random access response (RAR)during a RAR window, the window starts at the first symbol of theearliest CORESET the UE is configured to receive PDCCH for Type1-PDCCHcommon search space (CSS) set, that is at least one symbol, after thelast symbol of the PRACH occasion corresponding to the last PRACHtransmission.

Example A12 may include the method of example A1 or some other exampleherein, wherein separate PRACH occasions can be configured for PRACHrepetition from legacy 4-step and/or 2-step RACH, respectively

Example A13 may include the method of example A1 or some other exampleherein, wherein shared PRACH occasions, but different PRACH preamblescan be configured for PRACH repetition from legacy 4-step and/or 2-stepRACH, respectively.

Example A14 may include the method of example A1 or some other exampleherein, wherein within the set of preambles associated with a same SSB,PRACH preamble for PRACH repetition is allocated after contention basedrandom access (CBRA) 2-step RACH.

Example A15 may include the method of example A1 or some other exampleherein, wherein PRACH repetition for 4-step RACH is allocated within thepreambles for legacy CBRA 4-step RACH.

Example A16 may include the method of example A1 or some other exampleherein, wherein when measured Reference Signal Receive Power (RSRP) isless than or equal to a threshold which is configured by higher layersvia MSI, RMSI (SIB1), OSI or RRC signalling, UE may employ PRACHrepetition during PRACH repetition window.

Example A17 may include the method of example A1 or some other exampleherein, wherein when path-loss is greater than or equal to a thresholdwhich is configured by higher layers via MSI, RMSI (SIB1), OSI or RRCsignalling, UE may employ PRACH repetition during PRACH repetitionwindow

Example A18 may include the method of example A1 or some other exampleherein, wherein PRACH repetition may also apply for contention freerandom access (CFRA) procedure, wherein dedicated PRACH preamble forPRACH repetition, and PRACH repetition window (which may includestarting position and number of repetitions or duration of PRACHrepetitions) may be configured by dedicated RRC signalling.

Example A19 may include a method comprising: receiving, from a gNodeB(gNB), configuration information to indicate a repetition window and/ora number of repetitions for a physical random access channel (PRACH);and encoding a PRACH message for transmission with repetition within therepetition window.

Example A20 may include the method of example A19 or some other exampleherein, wherein the repetition window includes a plurality of PRACHoccasions.

Example A21 may include the method of example A19-A20 or some otherexample herein, wherein the configuration information includes astarting position of a PRACH occasion associated with the repetitionwindow.

Example A22 may include the method of example A19-A21 or some otherexample herein, wherein the configuration information is received viaminimum system information (MSI), remaining minimum system information(RMSI), other system information (OSI), and/or dedicated radio resourcecontrol (RRC) signalling

Example A23 may include the method of example A19-A22 or some otherexample herein, wherein the repetition window is aligned with anassociation period or an association pattern period for mapping SSBindexes to PRACH occasions.

Example A24 may include the method of example A19-A23 or some otherexample herein, wherein, to indicate the repetition window, theconfiguration information includes an offset and a periodicity.

Example A25 may include the method of example A24 or some other exampleherein, wherein the offset is a slot offset, a symbol offset, or a frameoffset.

Example A26 may include the method of example A19-A25 or some otherexample herein, wherein the number of repetitions is for physicaldownlink control channel (PDCCH) order PRACH transmission

Example A27 may include the method of example A26 or some other exampleherein, wherein the number of repetitions is received via RRC signallingand/or DCI.

Example A28 may include the method of example A19-A27 or some otherexample herein, wherein the repetitions of the PRACH message aretransmitted with a same transmit beam or different transmit beams withinthe repetition window.

Example A29 may include the method of example A19-A28 or some otherexample herein, further comprising receiving an indication of whetherthe same beam or different beams are to be used for the repetitions ofthe PRACH message within the repetition window.

Example A30 may include the method of example A29 or some other exampleherein, wherein the indication is received via MSI, RMSI (e.g., SIB1),OSI, and/or RRC signalling.

Example A31 may include the method of example A19-A30 or some otherexample herein, further comprising, if multiple PRACH occasions withPRACH repetition window associated with same synchronization signalblock (SSB) index are multiplexed in a frequency division multiplexing(FDM) manner, the PRACH message is transmitted in only one PRACHoccasion of the repetition window.

Example A32 may include the method of example A31 or some other exampleherein, wherein the only one PRACH occasion is the PRACH occasion (RO)with a lowest index or a randomly selected PRACH occasion.

Example A33 may include the method of example A20-A32 or some otherexample herein, wherein the PRACH occasions for the repetitions areassociated with a same SSB for determination of transmit power, pathloss, and/or reference signal received power.

Example A34 may include the method of example A20-A32 or some otherexample herein, wherein the PRACH occasions for the repetitions areassociated with different SSBs for determination of transmit power, pathloss, and/or reference signal received power.

Example A35 may include the method of example A19-A34 or some otherexample herein, wherein the PRACH message is a PRACH preamble.

Example A36 may include the method of example A19-A35 or some otherexample herein, further comprising monitoring for a random accessresponse (RAR) during a RAR window, wherein the RAR window starts at afirst symbol of the earliest CORESET the UE is configured to receivePDCCH for Type1-PDCCH common search space (CSS) set, that is at leastone symbol, after the last symbol of the PRACH occasion corresponding tothe last PRACH transmission.

Example A37 may include the method of example A20-A36 or some otherexample herein, wherein separate PRACH occasions are configured forPRACH repetition 4-step RACH and 2-step RACH, respectively.

Example A38 may include the method of example A20-A36 or some otherexample herein, wherein the PRACH occasions are shared for 4-step RACHand 2-step RACH.

Example A39 may include the method of example A38 or some other exampleherein, wherein different PRACH preambles are configured for 4-step RACHand 2-step RACH.

Example A40 may include the method of example A19-A39 or some otherexample herein, wherein the PRACH message is repeated based on adetermination that a measured Reference Signal Receive Power (RSRP) isless than or equal to a threshold.

Example A41 may include the method of example A19-A40 or some otherexample herein, wherein the PRACH message is repeated based on adetermination that a measured path loss is less than or equal to athreshold.

Example A42 may include the method of example AA40-41 or some otherexample herein, further comprising receiving an indication of thethreshold via MSI, RMSI (e.g., SIB1), OSI, and/or RRC signalling,

Example A43 may include the method of example A19-A42 or some otherexample herein, wherein the configuration information is used for acontention free random access (CFRA) procedure.

Example A44 may include the method of example A19-A43 or some otherexample herein, wherein the method is performed by a UE or a portionthereof.

Example A45 may include a method comprising: encoding, for transmissionto a UE, configuration information to indicate a repetition windowand/or a number of repetitions for a physical random access channel(PRACH); and receiving, from the UE, a PRACH message with repetitionwithin the repetition window.

Example A46 may include the method of example A45 or some other exampleherein, wherein the repetition window includes a plurality of PRACHoccasions.

Example A47 may include the method of example A45-A46 or some otherexample herein, wherein the configuration information includes astarting position of a PRACH occasion associated with the repetitionwindow.

Example A48 may include the method of example A45-A47 or some otherexample herein, wherein the configuration information is transmitted viaminimum system information (MR), remaining minimum system information(RMSI), other system information (OSI), and/or dedicated radio resourcecontrol (RRC) signalling

Example A49 may include the method of example A45-A48 or some otherexample herein, wherein the repetition window is aligned with anassociation period or an association pattern period for mapping SSBindexes to PRACH occasions.

Example A50 may include the method of example A45-A49 or some otherexample herein, wherein the method is performed by a gNB or a portionthereof.

Example B1 may include a method of wireless communication for a fifthgeneration (5G) or new radio (NR) system, the method comprising:receiving, by a UE from a gNodeB, an indication of a number ofrepetitions for a channel state information (CSI) report on a physicaluplink shared channel (PUSCH); and transmitting, by the UE, the CSIreport with repetition on the PUSCH.

Example B2 may include the method of example B1 or some other exampleherein, wherein the CSI report includes aperiodic CSI (A-CSI) reportand/or semi-persistent CSI (SP-CSI) report.

Example B3 may include the method of example B1 or some other exampleherein, wherein whether repetition of CSI report on PUSCH is enabled canbe configured by higher layers via minimum system information (MSI),remaining minimum system information (RMSI), other system information(OSI) or dedicated radio resource control (RRC) signalling.

Example B4 may include the method of example B1 or some other exampleherein, wherein number of repetitions for CSI report on PUSCH may beseparately configured or indicated from the number of repetitions forPUSCH; wherein if not configured, the number of repetitions for CSIreport on PUSCH can use the one which is configured or indicated for thePUS CH transmission.

Example B5 may include the method of example B1 or some other exampleherein, wherein for PUSCH repetition type A, number of repetitions forCSI report on PUSCH can be separately configured frompusch-AggregationFactor or separately indicated from numberofrepetitionsas part of PUSCH time domain resource assignment (TDRA) indication byDCI formats 0_1 or 0_2

Example B6 may include the method of example B1 or some other exampleherein, wherein for PUSCH repetition type B, number of repetitions forCSI report on PUSCH can be separately indicated from numberofrepetitionsas part of TDRA indication by DCI formats 0_1 or 0_2.

Example B7 may include the method of example B1 or some other exampleherein, wherein when A-CSI is multiplexed on PUSCH with transport block,the number of repetitions of A-CSI may follow the number of repetitionsfor PUSCH.

Example B8 may include the method of example B1 or some other exampleherein, wherein the numbers of repetitions for A-CSI on PUSCH may followthe value that may be provided separately from pusch-AggregationFactoror numberofrepetitions.

Example B9 may include the method of example B1 or some other exampleherein, wherein when A-CSI or SP-CSI is multiplexed on PUSCH with notransport block, the number of repetitions of CSI report on PUSCH mayfollow the number of repetitions which is configured for CSI report onPUSCH

Example B10 may include the method of example B1 or some other exampleherein, wherein for PUSCH repetition type B, A-CSI or SP-CSI report maybe carried on each nominal repetition.

Example B11 may include the method of example B1 or some other exampleherein, wherein for PUSCH repetition Type B, when a UE receives a DCIthat schedules aperiodic CSI report(s) or activates semi-persistent CSIreport(s) on PUSCH with no transport block by a CSI request field on aDCI, UE shall transmit A-CSI or SP-CSI reports on each actual repetitionthat is same as the indicated nominal repetition

Example B12 may include the method of example B1 or some other exampleherein, wherein when one nominal repetition is segmented into more thanone actual repetition due to across slot boundary, conflict with invalidsymbols or semi-static DL symbols, actual repetitions are dropped.

Example B13 may include the method of example B1 or some other exampleherein, wherein for PUSCH repetition Type B, when a UE receives a DCIthat schedules aperiodic CSI report(s) or activates semi-persistent CSIreport(s) on PUSCH with transport block by a CSI request field on a DCI,UE shall transmit A-CSI or SP-CSI reports with transport block on eachactual repetition that is same as the indicated nominal repetition.

Example B14 may include the method of example B1 or some other exampleherein, wherein UE shall transmit only transport block without A-CSI orSP-CSI report on actual repetition when actual repetition is not same asnominal repetition.

Example B15 may include the method of example B1 or some other exampleherein, wherein for PUSCH repetition type B, when the number of bits forCSI report is less than or equal to 11 bits, CSI report is carried ineach actual repetition regardless of whether transport block is presenton PUSCH.

Example B16 may include the method of example B1 or some other exampleherein, wherein for PUSCH repetition type B, part of symbols fromnominal repetition may be repeated and transmitted in actual repetition.

Example B17 may include the method of example B1 or some other exampleherein, wherein for PUSCH repetition type B, CSI report is carried ineach actual repetition regardless of whether transport block is presenton PUSCH.

Example B18 may include the method of example B1 or some other exampleherein, wherein the total number of REs for PUSCH for determination ofthe REs for A-CSI/SP-CSI part 1 and part 2 may be calculated from thenominal repetition length

Example B19 may include the method of example B1 or some other exampleherein, wherein the total number of REs for PUSCH for determination ofthe REs for A-CSI/SP-CSI part 1 and part 2 may be calculated from anactual repetition length.

Example B20 may include a method comprising: receiving configurationinformation to indicate a number of repetitions for a channel stateinformation (CSI) report on a physical uplink shared channel (PUSCH);and encoding, for transmission on the PUSCH, the CSI report with theindicated number of repetitions.

Example B21 may include the method of example B20 or some other exampleherein, wherein the CSI report includes an aperiodic CSI (A-CSI) reportand/or a semi-persistent CSI (SP-CSI) report.

Example B22 may include the method of example B20-B21 or some otherexample herein, wherein the configuration information is received viaminimum system information (MR), remaining minimum system information(RMSI), other system information (OSI), and/or dedicated radio resourcecontrol (RRC) signalling.

Example B23 may include the method of example B20-B22 or some otherexample herein, wherein the number of repetitions corresponds to anumber of repetitions for a PUSCH.

Example B24 may include the method of example B20-B23 or some otherexample herein, wherein for PUSCH repetition type A, the indication ofthe number of repetitions is separate from a pusch-AggregationFactorand/or a numberofrepetitions as part of PUSCH time domain resourceassignment (TDRA) indication by DCI formats 0_1 or 0_2.

Example B25 may include the method of example B20-B24 or some otherexample herein, wherein for PUSCH repetition type B, the indication ofthe number of repetitions for CSI report is separate from anumberofrepetitions as part of TDRA indication by DCI formats 0_1 or0_2.

Example B26 may include the method of example B20-B25 or some otherexample herein, wherein the CSI is A-CSI multiplexed on the PUSCH with atransport block, and wherein the number of repetitions of the A-CSI isthe same as a number of repetitions for the PUSCH.

Example B27 may include the method of example B20-B26 or some otherexample herein, wherein the method is performed by a UE or a portionthereof.

Example B28 may include a method comprising: encoding, for transmissionto a user equipment (UE), configuration information to indicate a numberof repetitions for a channel state information (CSI) report on aphysical uplink shared channel (PUSCH); and receiving the CSI report onthe PUSCH with the indicated number of repetitions.

Example B29 may include the method of example B28 or some other exampleherein, wherein the CSI report includes an aperiodic CSI (A-CSI) reportand/or a semi-persistent CSI (SP-CSI) report.

Example B30 may include the method of example B28-B29 or some otherexample herein, wherein the configuration information is transmitted viaminimum system information (MR), remaining minimum system information(RMSI), other system information (OSI), and/or dedicated radio resourcecontrol (RRC) signalling.

Example B31 may include the method of example B28-B30 or some otherexample herein, wherein the number of repetitions corresponds to anumber of repetitions for a PUSCH.

Example B32 may include the method of example B28-B31 or some otherexample herein, wherein for PUSCH repetition type A, the indication ofthe number of repetitions is separate from a pusch-AggregationFactorand/or a numberofrepetitions as part of PUSCH time domain resourceassignment (TDRA) indication by DCI formats 0_1 or 0_2.

Example B33 may include the method of example B28-B32 or some otherexample herein, wherein for PUSCH repetition type B, the indication ofthe number of repetitions for CSI report is separate from anumberofrepetitions as part of TDRA indication by DCI formats 0_1 or0_2.

Example B34 may include the method of example B28-B33 or some otherexample herein, wherein the CSI is A-CSI multiplexed on the PUSCH with atransport block, and wherein the number of repetitions of the A-CSI isthe same as a number of repetitions for the PUSCH.

Example B35 may include the method of example B28-B34 or some otherexample herein, wherein the method is performed by a gNB or a portionthereof.

Example C1 may include one or more non-transitory computer-readablemedia (NTCRM) having instructions, stored thereon, that when executed byone or more processors of a user equipment (UE) cause the UE to: receiveconfiguration information to configure repetitions of a channel stateinformation (CSI) report on a physical uplink shared channel (PUSCH),wherein the CSI report includes an aperiodic CSI (A-CSI) report or asemi-persistent CSI (SP-CSI) report; receive a DCI to trigger the A-CSIreport or activate the SP-CSI report; and encode, for transmission onthe PUSCH, the CSI report with repetitions based on the configurationinformation and the DCI.

Example C2 may include the one or more NTCRM of example C1, wherein theconfiguration information indicates a number of the repetitions.

Example C3 may include the one or more NTCRM of example C2, wherein thenumber of repetitions is indicated separately from a number ofrepetitions of the PUSCH.

Example C4 may include the one or more NTCRM of example C1, wherein theconfiguration information is received via one or more of minimum systeminformation (MR), remaining minimum system information (RMSI), othersystem information (OSI), or dedicated radio resource control (RRC)signaling.

Example C5 may include the one or more NTCRM of example C1, wherein theconfiguration information is configured per DCI format.

Example C6 may include the one or more NTCRM of example C1, wherein theCSI report is the A-CSI report and is multiplexed on the PUSCH with atransport block, and wherein a number of the repetitions of the A-CSI isthe same as a number of repetitions for the PUSCH.

Example C7 may include one or more non-transitory computer-readablemedia (NTCRM) having instructions, stored thereon, that when executed byone or more processors of a next generation Node B (gNB) cause the gNBto: encode, for transmission to a user equipment (UE), configurationinformation to configure repetitions of a channel state information(CSI) report on a physical uplink shared channel (PUSCH), wherein theCSI report includes an aperiodic CSI (A-CSI) report or a semi-persistentCSI (SP-CSI) report; encode, for transmission to the UE, a DCI totrigger the A-CSI report or activate the SP-CSI report; and receive,from the UE on the PUSCH, the CSI report with repetitions based on theconfiguration information and the DCI.

Example C8 may include the one or more NTCRM of example C7, wherein theconfiguration information indicates a number of the repetitions.

Example C9 may include the one or more NTCRM of example C8, wherein thenumber of repetitions is indicated separately from a number ofrepetitions of the PUSCH.

Example C10 may include the one or more NTCRM of example C7, wherein theconfiguration information is transmitted via one or more of minimumsystem information (MSI), remaining minimum system information (RMSI),other system information (OSI), or dedicated radio resource control(RRC) signaling.

Example C11 may include the one or more NTCRM of example C7, wherein theconfiguration information is configured per DCI format.

Example C12 may include the one or more NTCRM of example C7, wherein theCSI report is the A-CSI report and is multiplexed on the PUSCH with atransport block, and wherein a number of the repetitions of the A-CSI isthe same as a number of repetitions for the PUSCH.

Example C13 may include one or more non-transitory computer-readablemedia (NTCRM) having instructions, stored thereon, that when executed byone or more processors of a user equipment (UE) cause the UE to:receive, from a gNodeB (gNB), configuration information to indicate arepetition window for a physical random access channel (PRACH), whereinthe repetition window includes a plurality of PRACH occasions; andencode a PRACH message for transmission with repetition in therespective PRACH occasions.

Example C14 may include the one or more NTCRM of example C13, whereinthe configuration information indicates a starting position and a numberof PRACH repetitions.

Example C15 may include the one or more NTCRM of example C13, whereinthe configuration information is received via one or more of minimumsystem information (MSI), remaining minimum system information (RMSI),other system information (OSI), or dedicated radio resource control(RRC) signaling.

Example C16 may include the one or more NTCRM of example C13, wherein,to indicate the repetition window, the configuration informationincludes an offset and a periodicity, wherein the offset is a slotoffset, a symbol offset, or a frame offset.

Example C17 may include the one or more NTCRM of example C13, whereinthe configuration information includes an indication of whether the samebeam or different beams are to be used for the repetitions of the PRACHmessage within the repetition window.

Example C18 may include the one or more NTCRM of example C13, wherein ifthe plurality of PRACH occasions in the repetition window associated asame synchronization signal block (SSB) index are multiplexed in afrequency division multiplexing (FDM) manner, the PRACH message istransmitted in only one PRACH occasion of the repetition window.

Example C19 may include the one or more NTCRM of example C13, whereinthe PRACH occasions for the repetitions are associated with a samesynchronization signal block (SSB) for determination of transmit power,path loss, and reference signal received power.

Example C20 may include the one or more NTCRM of example C13, whereinthe PRACH occasions for the repetitions are associated with differentsynchronization signal blocks (SSBs) for determination of transmitpower, path loss, and reference signal received power.

Example Z01 may include an apparatus comprising means to perform one ormore elements of a method described in or related to any of examplesA1-A50, B1-B35, C1-C20, or any other method or process described herein.

Example Z02 may include one or more non-transitory computer-readablemedia comprising instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform one or more elements of a method describedin or related to any of examples A1-A50, B1-B35, C1-C20, or any othermethod or process described herein.

Example Z03 may include an apparatus comprising logic, modules, orcircuitry to perform one or more elements of a method described in orrelated to any of examples A1-A50, B1-B35, C1-C20, or any other methodor process described herein.

Example Z04 may include a method, technique, or process as described inor related to any of examples A1-A50, B1-B35, C1-C20, or portions orparts thereof.

Example Z05 may include an apparatus comprising: one or more processorsand one or more computer-readable media comprising instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform the method, techniques, or process as described inor related to any of examples A1-A50, B1-B35, C1-C20, or portionsthereof.

Example Z06 may include a signal as described in or related to any ofexamples A1-A50, B1-B35, C1-C20, or portions or parts thereof.

Example Z07 may include a datagram, packet, frame, segment, protocoldata unit (PDU), or message as described in or related to any ofexamples A1-A50, B1-B35, C1-C20, or portions or parts thereof, orotherwise described in the present disclosure.

Example Z08 may include a signal encoded with data as described in orrelated to any of examples A1-A50, B1-B35, C1-C20, or portions or partsthereof, or otherwise described in the present disclosure.

Example Z09 may include a signal encoded with a datagram, packet, frame,segment, protocol data unit (PDU), or message as described in or relatedto any of examples A1-A50, B1-B35, C1-C20, or portions or parts thereof,or otherwise described in the present disclosure.

Example Z10 may include an electromagnetic signal carryingcomputer-readable instructions, wherein execution of thecomputer-readable instructions by one or more processors is to cause theone or more processors to perform the method, techniques, or process asdescribed in or related to any of examples A1-A50, B1-B35, C1-C20, orportions thereof.

Example Z11 may include a computer program comprising instructions,wherein execution of the program by a processing element is to cause theprocessing element to carry out the method, techniques, or process asdescribed in or related to any of examples A1-A50, B1-B35, C1-C20, orportions thereof.

Example Z12 may include a signal in a wireless network as shown anddescribed herein.

Example Z13 may include a method of communicating in a wireless networkas shown and described herein.

Example Z14 may include a system for providing wireless communication asshown and described herein.

Example Z15 may include a device for providing wireless communication asshown and described herein.

Any of the above-described examples may be combined with any otherexample (or combination of examples), unless explicitly statedotherwise. The foregoing description of one or more implementationsprovides illustration and description, but is not intended to beexhaustive or to limit the scope of embodiments to the precise formdisclosed. Modifications and variations are possible in light of theabove teachings or may be acquired from practice of various embodiments.

Abbreviations

Unless used differently herein, terms, definitions, and abbreviationsmay be consistent with terms, definitions, and abbreviations defined in3GPP TR 21.905 v16.0.0 (2019-06). For the purposes of the presentdocument, the following abbreviations may apply to the examples andembodiments discussed herein.

3GPP Third Generation ASN.1 Abstract Syntax Certification PartnershipProject Notation One Authority 4G Fourth Generation AUSF AuthenticationCAPEX CAPital 5G Fifth Generation Server Function EXpenditure 5GC 5GCore network AWGN Additive CBRA Contention Based ACK AcknowledgementWhite Gaussian Random Access AF Application Noise CC Component Carrier,Function BAP Backhaul Country Code, AM Acknowledged Adaptation ProtocolCryptographic Mode BCH Broadcast Channel Checksum AMBRAggregate BER BitError Ratio CCA Clear Channel Maximum Bit Rate BFD Beam FailureAssessment AMF Access and Detection CCE Control Channel Mobility BLERBlock Error Rate Element Management BPSK Binary Phase Shift CCCH CommonControl Function Keying Channel AN Access Network BRAS Broadband RemoteCE Coverage ANR Automatic Access Server Enhancement Neighbour RelationBSS Business Support CDM Content Delivery AP Application System NetworkProtocol, Antenna BS Base Station CDMA Code- Port, Access Point BSRBuffer Status Division Multiple API Application Report AccessProgramming Interface BW Bandwidth CFRA Contention Free APN Access PointName BWP Bandwidth Part Random Access ARP Allocation and C-RNTI CellRadio CG Cell Group Retention Priority Network Temporary CI CellIdentity ARQ Automatic Repeat Identity CID Cell-ID (e.g., Request CACarrier positioning method) AS Access Stratum Aggregation, CIM CommonCIR Carrier to CPU CSI processing Information Model Interference Ratiounit, Central Processing CSI-RSRQ CSI CK Cipher Key Unit referencesignal CM Connection C/R received quality Management, ConditionalCommand/Response CSI-SINR CSI signal- Mandatory field bit to-noise andinterference CMAS Commercial CRAN Cloud Radio ratio Mobile Alert ServiceAccess Network, CSMA Carrier Sense CMD Command Cloud RAN Multiple AccessCMS Cloud Management CRB Common Resource CSMA/CA CSMA with System Blockcollision avoidance CO Conditional CRC Cyclic Redundancy CSS CommonSearch Optional Check Space, Cell-specific CoMP Coordinated Multi- CRIChannel-State Search Space Point Information Resource CTS Clear-to-SendCORESET Control Indicator, CSI-RS CW Codeword Resource Set ResourceIndicator CWS Contention COTS Commercial Off- C-RNTI Cell RNTI WindowSize The-Shelf CS Circuit Switched D2D Device-to-Device CP ControlPlane, CSAR Cloud Service DC Dual Connectivity, Cyclic Prefix,Connection Archive Direct Current Point CSI Channel-State DCI DownlinkControl CPD Connection Point Information Information Descriptor CSI-IMCSI DF Deployment CPE Customer Premise Interference Flavour EquipmentMeasurement DL Downlink CPICHCommon Pilot CSI-RS CSI DMTF DistributedChannel Reference Signal Management Task Force CQI Channel QualityCSI-RSRP CSI DPDK Data Plane Indicator reference signal Development KitDM-RS, DMRS received power EREG enhanced REG, Demodulation Managementenhanced resource Reference Signal Function element groups DN Datanetwork EGPRS Enhanced ETSI European DRB Data Radio Bearer GPRSTelecommunications DRS Discovery EIR Equipment Identity StandardsInstitute Reference Signal Register ETWS Earthquake and DRXDiscontinuous eLAA enhanced Licensed Tsunami Warning Reception AssistedAccess, System DSL Domain Specific enhanced LAA eUICC embedded UICC,Language. Digital EM Element Manager embedded Universal Subscriber LineeMBB Enhanced Mobile Integrated Circuit Card DSLAM DSL Access BroadbandE-UTRA Evolved Multiplexer EMS Element UTRA DwPTS Downlink ManagementSystem E-UTRAN Evolved Pilot Time Slot eNB evolved NodeB, E- UTRAN E-LANEthernet UTRAN Node B EV2X Enhanced V2X Local Area Network EN-DC E-UTRA-F1AP F1 Application E2E End-to-End NR Dual Protocol ECCA extended clearConnectivity F1-C F1 Control plane channel assessment, EPC EvolvedPacket interface extended CCA Core F1-U F1 User plane ECCE EnhancedControl EPDCCH enhanced interface Channel Element, PDCCH, enhanced FACCHFast Enhanced CCE Physical Downlink Associated Control ED EnergyDetection Control Cannel CHannel EDGE Enhanced Datarates EPRE Energy perFACCH/F Fast for GSM Evolution resource element Associated Control (GSMEvolution) EPS Evolved Packet Channel/Full rate EGMF Exposure SystemGNSS Global Navigation Governance FN Frame Number Satellite SystemFACCH/H Fast FPGA Field- GPRS General Packet Associated ControlProgrammable Gate Radio Service Channel/Half rate Array GSM GlobalSystem for FACH Forward Access FR Frequency Range Mobile Channel G-RNTIGERAN Communications, FAUSCH Fast Uplink Radio Network Groupe SpécialSignalling Channel Temporary Identity Mobile FB Functional Block GERANGTP GPRS Tunneling FBI Feedback GSM EDGE RAN, Protocol Information GSMEDGE Radio GTP-UGPRS Tunnelling FCC Federal Access Network Protocol forUser Communications GGSN Gateway GPRS Plane Commission Support Node GTSGo To Sleep Signal FCCH Frequency GLONASS (related to WUS) CorrectionCHannel GLObal'naya GUMMEI Globally FDD Frequency DivisionNAvigatsionnaya Unique MME Identifier Duplex Sputnikovaya GUTI GloballyUnique FDM Frequency Division Sistema (Engl.: Temporary UE IdentityMultiplex Global Navigation HARQ Hybrid ARQ, FDMAFrequency DivisionSatellite System) Hybrid Automatic Multiple Access gNB Next GenerationRepeat Request FE Front End NodeB HANDO Handover FEC Forward ErrorgNB-CU gNB- HFN HyperFrame Correction centralized unit, Next Number FFSFor Further Study Generation NodeB HHO Hard Handover FFT Fast Fouriercentralized unit HLR Home Location Transformation gNB-DU gNB- RegisterfeLAA further enhanced distributed unit, Next HN Home Network LicensedAssisted Generation NodeB HO Handover Access, further distributed unitIMPU IP Multimedia enhanced LAA IDFT Inverse Discrete PUblic identityHPLMN Home Fourier Transform IMS IP Multimedia Public Land Mobile IEInformation Subsystem Network element IMSI International HSDPA HighSpeed IBE In-Band Emission Mobile Subscriber Downlink Packet IEEEInstitute of Identity Access Electrical and Electronics IoT Internet ofThings HSN Hopping Sequence Engineers IP Internet Protocol Number IEIInformation Ipsec IP Security, HSPA High Speed Packet Element IdentifierInternet Protocol Access IEIDL Information Security HSS Home SubscriberElement Identifier IP-CAN IP- Server Data Length Connectivity AccessHSUPA High Speed IETF Internet Network Uplink Packet Access EngineeringTask IP-M IP Multicast HTTP Hyper Text Force IPv4 Internet ProtocolTransfer Protocol IF Infrastructure Version 4 HTTPS Hyper Text IMInterference IPv6 Internet Protocol Transfer Protocol Measurement,Version 6 Secure (https is Intermodulation, IP IR Infrared http/1.1 overSSL, Multimedia IS In Sync i.e. port 443) IMC IMS Credentials IRPIntegration I-Block Information IMEI International Reference Point BlockMobile Equipment ISDN Integrated Services ICCID Integrated CircuitIdentity Digital Network Card Identification IMGI International ISIM IMServices IAB Integrated Access mobile group identity Identity Module andBackhaul IMPI IP Multimedia ISO International ICIC Inter-Cell PrivateIdentity Organisation for Interference L2 Layer 2 (data linkStandardisation Coordination layer) LWIP LTE/WLAN Radio ID Identity,identifier L3 Layer 3 (network Level Integration with ISP InternetService layer) IPsec Tunnel Provider LAA Licensed Assisted LTE Long TermIWF Interworking- Access Evolution Function LAN Local Area M2MMachine-to- I-WLAN Network Machine Interworking LBT Listen Before TalkMAC Medium Access WLAN LCM LifeCycle Control (protocol Constraint lengthof Management layering context) the convolutional code, LCR Low ChipRate MAC Message USIM Individual key LCS Location Servicesauthentication code kB Kilobyte (1000 LCID Logical (security/encryptionbytes) Channel ID context) kbps kilo-bits per second LI Layer IndicatorMAC-A MAC used Kc Ciphering key LLC Logical Link for authentication andKi Individual Control, Low Layer key agreement (TSG T subscriberCompatibility WG3 context) authentication key LPLMN Local MAC-IMAC usedfor data KPI Key Performance PLMN integrity of Indicator LPP LTEPositioning signalling messages (TSG KQI Key Quality Protocol T WG3context) Indicator LSB Least Significant MANO KSI Key Set Identifier BitManagement and ksps kilo-symbols per LTE Long Term Orchestration secondEvolution MBMS Multimedia KVM Kernel Virtual LWA LTE-WLAN Broadcast andMulticast Machine aggregation Service L1 Layer 1 (physical MM MobilityMBSFN Multimedia layer) Management Broadcast multicast L1-RSRP Layer 1MME Mobility MSC Mobile Switching reference signal Management EntityCentre received power MN Master Node MSI Minimum System service SingleFrequency MnS Management Information, MCH Network Service Scheduling MCCMobile Country MO Measurement Information Code Object, Mobile MSIDMobile Station MCG Master Cell Group Originated Identifier MCOT MaximumChannel MPBCH MTC MSIN Mobile Station Occupancy Time Physical BroadcastIdentification MCS Modulation and CHannel Number coding scheme MPDCCHMTC MSISDN Mobile MDAF Management Data Physical Downlink Subscriber ISDNAnalytics Function Control CHannel Number MDAS Management Data MPDSCHMTC MT Mobile Terminated, Analytics Service Physical Downlink MobileTermination MDT Minimization of Shared CHannel MTC Machine-Type DriveTests MPRACH MTC Communications ME Mobile Equipment Physical RandommMTCmassive MTC, MeNB master eNB Access CHannel massive Machine- MERMessage Error MPUSCH MTC Type Communications Ratio Physical UplinkShared MU-MIMO Multi User MGL Measurement Gap Channel MIMO Length MPLSMultiProtocol MWUS MTC wake- MGRP Measurement Gap Label Switching upsignal, MTC Repetition Period MS Mobile Station WUS MIB MasterInformation MSB Most Significant NACK Negative Block, Management BitAcknowledgement Information Base NMS Network NAI Network Access MIMOMultiple Input Management System Identifier Multiple Output N-PoPNetwork Point of NRF NF Repository MLC Mobile Location Presence FunctionCentre NMIB, N-MIB NRS Narrowband NAS Non-Access Narrowband MIBReference Signal Stratum, Non- Access NPBCH Narrowband NS NetworkService Stratum layer Physical Broadcast NSA Non-Standalone NCT NetworkCHannel operation mode Connectivity Topology NPDCCH Narrowband NSDNetwork Service NC-JT Non- Physical Downlink Descriptor Coherent JointControl CHannel NSR Network Service Transmission NPDSCH NarrowbandRecord NEC Network Capability Physical Downlink NSSAINetwork SliceExposure Shared CHannel Selection Assistance NE-DC NR-E- NPRACHNarrowband Information UTRA Dual Physical Random S-NNSAI Single-Connectivity Access CHannel NSSAI NEF Network Exposure NPUSCH NarrowbandNSSF Network Slice Function Physical Uplink Selection Function NFNetwork Function Shared CHannel NW Network NFP Network NPSS NarrowbandNWUSNarrowband wake- Forwarding Path Primary up signal, Narrowband NFPDNetwork Synchronization WUS Forwarding Path Signal NZP Non-Zero PowerDescriptor NSSS Narrowband O&M Operation and NFV Network FunctionsSecondary Maintenance Virtualization Synchronization ODU2 Opticalchannel NFVI NFV Infrastructure Signal Data Unit - type 2 NFVO NFVOrchestrator NR New Radio, OFDM Orthogonal NG Next Generation, NeighbourRelation Frequency Division Next Gen PCF Policy Control MultiplexingNGEN-DC NG-RAN Function PLMN Public Land Mobile E-UTRA-NR Dual PCRFPolicy Control and Network Connectivity Charging Rules PIN Personal NMNetwork Manager Function Identification Number OFDMA Orthogonal PDCPPacket Data PM Performance Frequency Division Convergence Protocol,Measurement Multiple Access Packet Data PMI Precoding Matrix OOBOut-of-band Convergence Indicator OOS Out of Sync Protocol layer PNFPhysical Network OPEX OPerating EXpense PDCCH Physical Function OSIOther System Downlink Control PNFD Physical Network Information ChannelFunction Descriptor OSS Operations Support PDCP Packet Data PNFRPhysical Network System Convergence Protocol Function Record OTAover-the-air PDN Packet Data POC PTT over Cellular PAPR Peak-to-AverageNetwork, Public Data PP, PTP Point-to- Power Ratio Network Point PARPeak to Average PDSCH Physical PPP Point-to-Point Ratio Downlink SharedProtocol PBCH Physical Broadcast Channel PRACH Physical Channel PDUProtocol Data Unit RACH PC Power Control, PEI Permanent PRB Physicalresource Personal Computer Equipment Identifiers block PCC Primary PFDPacket Flow PRG Physical resource Component Carrier, Description blockgroup Primary CC P-GW PDN Gateway ProSe Proximity Services, PCellPrimary Cell PHICH Physical Proximity-Based PCI Physical Cell ID,hybrid-ARQ indicator Service Physical Cell channel PRS PositioningIdentity PHY Physical layer Reference Signal PCEF Policy and PUSCHPhysical RAR Random Access Charging Uplink Shared Response EnforcementChannel RAT Radio Access Function QAM Quadrature Technology PRR PacketReception Amplitude Modulation RAU Routing Area Radio QCI QoS class ofUpdate PS Packet Services identifier RB Resource block, PSBCH PhysicalQCL Quasi co-location Radio Bearer Sidelink Broadcast QFI QoS Flow ID,QoS RBG Resource block Channel Flow Identifier group PSDCH Physical QoSQuality of Service REG Resource Element Sidelink Downlink QPSKQuadrature Group Channel (Quaternary) Phase Shift Rel Release PSCCHPhysical Keying REQ REQuest Sidelink Control QZSS Quasi-Zenith RF RadioFrequency Channel Satellite System RI Rank Indicator PSFCH PhysicalRA-RNTI Random RIV Resource indicator Sidelink Feedback Access RNTIvalue Channel RAB Radio Access RL Radio Link PSSCH Physical Bearer,Random RLC Radio Link Sidelink Shared Access Burst Control, Radio LinkChannel RACH Random Access Control layer PSCell Primary SCell ChannelRLC AM RLC PSS Primary RADIUS Remote Acknowledged Mode SynchronizationAuthentication Dial In RLC UM RLC Signal User Service UnacknowledgedMode PSTN Public Switched RAN Radio Access RLF Radio Link FailureTelephone Network Network RLM Radio Link PT-RS Phase-tracking RANDRANDom number Monitoring reference signal (used for RLM-RS Reference PTTPush-to-Talk authentication) Signal for RLM PUCCH Physical RTP Real TimeProtocol SCell Secondary Cell Uplink Control RTS Ready-To-Send SC-FDMASingle Channel RTT Round Trip Time Carrier Frequency RM Registration RxReception, Division Multiple Management Receiving, Receiver Access RMCReference S1AP S1 Application SCG Secondary Cell Measurement ChannelProtocol Group RMSI Remaining MSI, S1-MME S1 for the SCM SecurityContext Remaining Minimum control plane Management System InformationS1-U S1 for the user SCS Subcarrier Spacing RN Relay Node plane SCTPStream Control RNC Radio Network S-GW Serving Gateway TransmissionController S-RNTI SRNC Protocol RNL Radio Network Radio Network SDAPService Data Layer Temporary Identity Adaptation Protocol, RNTI RadioNetwork S-TMSI SAE Service Data Adaptation Temporary IdentifierTemporary Mobile Protocol layer ROHC RObust Header Station IdentifierSDL Supplementary Compression SA Standalone Downlink RRC Radio Resourceoperation mode SDNF Structured Data Control, Radio SAE System StorageNetwork Resource Control layer Architecture Evolution Function RRM RadioResource SAP Service Access SDP Session Description Management PointProtocol RS Reference Signal SAPD Service Access SDSF Structured DataRSRP Reference Signal Point Descriptor Storage Function Received PowerSAPI Service Access SDU Service Data Unit RSRQ Reference Signal PointIdentifier SEAF Security Anchor Received Quality SCC Secondary FunctionRSSI Received Signal Component Carrier, SeNB secondary eNB StrengthIndicator Secondary CC SS-RSRP RSU Road Side Unit SMF SessionSynchronization RSTD Reference Signal Management Function Signal basedReference Time difference SMS Short Message Signal Received SEPPSecurity Edge Service Power Protection Proxy SMSF SMS Function SS-RSRQSFI Slot format SMTC SSB-based Synchronization indication MeasurementTiming Signal based Reference SFTD Space-Frequency Configuration SignalReceived Time Diversity, SFN and SN Secondary Node, Quality frame timingdifference Sequence Number SS-SINR SFN System Frame SoC System on ChipSynchronization Number or SON Self-Organizing Signal based Signal toSingle Frequency Network Noise and Interference Network SpCell SpecialCell Ratio SgNB Secondary gNB SP-CSI-RNTISemi- SSS Secondary SGSNServing GPRS Persistent CSI RNTI Synchronization Support Node SPSSemi-Persistent Signal S-GW Serving Gateway Scheduling SSSG Search SpaceSet SI System Information SQN Sequence number Group SI-RNTI System SRScheduling Request SSSIF Search Space Set Information RNTI SRBSignalling Radio Indicator SIB System Information Bearer SSTSlice/Service Types Block SRS Sounding SU-MIMO Single User SIMSubscriber Identity Reference Signal MIMO Module SS Synchronization SULSupplementary SIP Session Initiated Signal Uplink Protocol SSB SS BlockTA Timing Advance, SiP System in Package SSBRI SSB Resource TrackingArea SL Sidelink Indicator TAC Tracking Area SLA Service Level SSCSession and Service Code Agreement Continuity UDP User Datagram SMSession TPMI Transmitted Protocol Management Precoding Matrix UDRUnified Data TAG Timing Advance Indicator Repository Group TR TechnicalReport UDSF Unstructured Data TAU Tracking Area TRP, TRxP StorageNetwork Update Transmission Function TB Transport Block Reception PointUICC Universal TBS Transport Block TRS Tracking Reference IntegratedCircuit Card Size Signal UL Uplink TBD To Be Defined TRx Transceiver UMUnacknowledged TCI Transmission TS Technical Mode ConfigurationIndicator Specifications, UML Unified Modelling TCP TransmissionTechnical Standard Language Communication TTI Transmission Time UMTSUniversal Mobile Protocol Interval Telecommunications TDD Time DivisionTx Transmission, System Duplex Transmitting, UP User Plane TDM TimeDivision Transmitter UPF User Plane Multiplexing U-RNTI UTRAN FunctionTDMATime Division Radio Network URI Uniform Resource Multiple AccessTemporary Identity Identifier TE Terminal UART Universal URL UniformResource Equipment Asynchronous Locator TEID Tunnel End Point Receiverand URLLC Ultra- Identifier Transmitter Reliable and Low TFT TrafficFlow UCI Uplink Control Latency Template Information USB UniversalSerial TMSI Temporary Mobile UE User Equipment Bus Subscriber IdentityUDM Unified Data USIM Universal TNL Transport Network ManagementSubscriber Identity Module Layer VLAN Virtual LAN, VRB Virtual ResourceTPC Transmit Power Virtual Local Area Block Control Network WiMAXWorldwide USS UE-specific search VM Virtual Machine Interoperability forspace VNF Virtualized Microwave Access UTRA UMTS Terrestrial NetworkFunction WLANWireless Local Radio Access VNFFG VNF Area Network UTRANUniversal Forwarding Graph WMAN Wireless Terrestrial Radio VNFFGD VNFMetropolitan Area Access Network Forwarding Graph Network UwPTS UplinkPilot Descriptor WPAN Wireless Personal Time Slot VNFM VNF Manager AreaNetwork V2I Vehicle-to- VoIP Voice-over-IP, X2-C X2-Control planeInfrastruction Voice-over-Internet X2-U X2-User plane V2P Vehicle-to-Protocol XML eXtensible Markup Pedestrian VPLMN Visited Language V2VVehicle-to-Vehicle Public Land Mobile XRES EXpected user V2X Vehicle-to-Network RESponse everything VPN Virtual Private XOR eXclusive OR VIMVirtualized Network ZC Zadoff-Chu Infrastructure Manager ZP Zero PowerVL Virtual Link,

Terminology

For the purposes of the present document, the following terms anddefinitions are applicable to the examples and embodiments discussedherein.

The term “circuitry” as used herein refers to, is part of, or includeshardware components such as an electronic circuit, a logic circuit, aprocessor (shared, dedicated, or group) and/or memory (shared,dedicated, or group), an Application Specific Integrated Circuit (ASIC),a field-programmable device (FPD) (e.g., a field-programmable gate array(FPGA), a programmable logic device (PLD), a complex PLD (CPLD), ahigh-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC),digital signal processors (DSPs), etc., that are configured to providethe described functionality. In some embodiments, the circuitry mayexecute one or more software or firmware programs to provide at leastsome of the described functionality. The term “circuitry” may also referto a combination of one or more hardware elements (or a combination ofcircuits used in an electrical or electronic system) with the programcode used to carry out the functionality of that program code. In theseembodiments, the combination of hardware elements and program code maybe referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, orincludes circuitry capable of sequentially and automatically carryingout a sequence of arithmetic or logical operations, or recording,storing, and/or transferring digital data. Processing circuitry mayinclude one or more processing cores to execute instructions and one ormore memory structures to store program and data information. The term“processor circuitry” may refer to one or more application processors,one or more baseband processors, a physical central processing unit(CPU), a single-core processor, a dual-core processor, a triple-coreprocessor, a quad-core processor, and/or any other device capable ofexecuting or otherwise operating computer-executable instructions, suchas program code, software modules, and/or functional processes.Processing circuitry may include more hardware accelerators, which maybe microprocessors, programmable processing devices, or the like. Theone or more hardware accelerators may include, for example, computervision (CV) and/or deep learning (DL) accelerators. The terms“application circuitry” and/or “baseband circuitry” may be consideredsynonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, orincludes circuitry that enables the exchange of information between twoor more components or devices. The term “interface circuitry” may referto one or more hardware interfaces, for example, buses, I/O interfaces,peripheral component interfaces, network interface cards, and/or thelike.

The term “user equipment” or “UE” as used herein refers to a device withradio communication capabilities and may describe a remote user ofnetwork resources in a communications network. The term “user equipment”or “UE” may be considered synonymous to, and may be referred to as,client, mobile, mobile device, mobile terminal, user terminal, mobileunit, mobile station, mobile user, subscriber, user, remote station,access agent, user agent, receiver, radio equipment, reconfigurableradio equipment, reconfigurable mobile device, etc. Furthermore, theterm “user equipment” or “UE” may include any type of wireless/wireddevice or any computing device including a wireless communicationsinterface.

The term “network element” as used herein refers to physical orvirtualized equipment and/or infrastructure used to provide wired orwireless communication network services. The term “network element” maybe considered synonymous to and/or referred to as a networked computer,networking hardware, network equipment, network node, router, switch,hub, bridge, radio network controller, RAN device, RAN node, gateway,server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any typeinterconnected electronic devices, computer devices, or componentsthereof. Additionally, the term “computer system” and/or “system” mayrefer to various components of a computer that are communicativelycoupled with one another. Furthermore, the term “computer system” and/or“system” may refer to multiple computer devices and/or multiplecomputing systems that are communicatively coupled with one another andconfigured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used hereinrefers to a computer device or computer system with program code (e.g.,software or firmware) that is specifically designed to provide aspecific computing resource. A “virtual appliance” is a virtual machineimage to be implemented by a hypervisor-equipped device that virtualizesor emulates a computer appliance or otherwise is dedicated to provide aspecific computing resource.

The term “resource” as used herein refers to a physical or virtualdevice, a physical or virtual component within a computing environment,and/or a physical or virtual component within a particular device, suchas computer devices, mechanical devices, memory space, processor/CPUtime, processor/CPU usage, processor and accelerator loads, hardwaretime or usage, electrical power, input/output operations, ports ornetwork sockets, channel/link allocation, throughput, memory usage,storage, network, database and applications, workload units, and/or thelike. A “hardware resource” may refer to compute, storage, and/ornetwork resources provided by physical hardware element(s). A“virtualized resource” may refer to compute, storage, and/or networkresources provided by virtualization infrastructure to an application,device, system, etc. The term “network resource” or “communicationresource” may refer to resources that are accessible by computerdevices/systems via a communications network. The term “systemresources” may refer to any kind of shared entities to provide services,and may include computing and/or network resources. System resources maybe considered as a set of coherent functions, network data objects orservices, accessible through a server where such system resources resideon a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium,either tangible or intangible, which is used to communicate data or adata stream. The term “channel” may be synonymous with and/or equivalentto “communications channel,” “data communications channel,”“transmission channel,” “data transmission channel,” “access channel,”“data access channel,” “link,” “data link,” “carrier,” “radiofrequencycarrier,” and/or any other like term denoting a pathway or mediumthrough which data is communicated. Additionally, the term “link” asused herein refers to a connection between two devices through a RAT forthe purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used hereinrefers to the creation of an instance. An “instance” also refers to aconcrete occurrence of an object, which may occur, for example, duringexecution of program code.

The terms “coupled,” “communicatively coupled,” along with derivativesthereof are used herein. The term “coupled” may mean two or moreelements are in direct physical or electrical contact with one another,may mean that two or more elements indirectly contact each other butstill cooperate or interact with each other, and/or may mean that one ormore other elements are coupled or connected between the elements thatare said to be coupled with each other. The term “directly coupled” maymean that two or more elements are in direct contact with one another.The term “communicatively coupled” may mean that two or more elementsmay be in contact with one another by a means of communication includingthrough a wire or other interconnect connection, through a wirelesscommunication channel or link, and/or the like.

The term “information element” refers to a structural element containingone or more fields. The term “field” refers to individual contents of aninformation element, or a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configurationconfigured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS/PBCH block.

The term “a “Primary Cell” refers to the MCG cell, operating on theprimary frequency, in which the UE either performs the initialconnection establishment procedure or initiates the connectionre-establishment procedure.

The term “Primary SCG Cell” refers to the SCG cell in which the UEperforms random access when performing the Reconfiguration with Syncprocedure for DC operation.

The term “Secondary Cell” refers to a cell providing additional radioresources on top of a Special Cell for a UE configured with CA.

The term “Secondary Cell Group” refers to the subset of serving cellscomprising the PSCell and zero or more secondary cells for a UEconfigured with DC.

The term “Serving Cell” refers to the primary cell for a UE inRRC_CONNECTED not configured with CA/DC there is only one serving cellcomprising of the primary cell.

The term “serving cell” or “serving cells” refers to the set of cellscomprising the Special Cell(s) and all secondary cells for a UE inRRC_CONNECTED configured with CA/.

The term “Special Cell” refers to the PCell of the MCG or the PSCell ofthe SCG for DC operation; otherwise, the term “Special Cell” refers tothe Pcell.

1. One or more non-transitory computer-readable media (NTCRM) havinginstructions, stored thereon, that when executed by one or moreprocessors of a user equipment (UE) cause the UE to: receiveconfiguration information to configure repetitions of a channel stateinformation (CSI) report on a physical uplink shared channel (PUSCH),wherein the CSI report includes an aperiodic CSI (A-CSI) report or asemi-persistent CSI (SP-CSI) report; receive a DCI to trigger the A-CSIreport or activate the SP-CSI report; and encode, for transmission onthe PUSCH, the CSI report with repetitions based on the configurationinformation and the DCI.
 2. The one or more NTCRM of claim 1, whereinthe configuration information indicates a number of the repetitions. 3.The one or more NTCRM of claim 2, wherein the number of repetitions isindicated separately from a number of repetitions of the PUSCH.
 4. Theone or more NTCRM of claim 1, wherein the configuration information isreceived via one or more of minimum system information (MSI), remainingminimum system information (RMSI), other system information (OSI), ordedicated radio resource control (RRC) signaling.
 5. The one or moreNTCRM of claim 1, wherein the configuration information is configuredper DCI format.
 6. The one or more NTCRM of claim 1, wherein the CSIreport is the A-CSI report and is multiplexed on the PUSCH with atransport block, and wherein a number of the repetitions of the A-CSI isthe same as a number of repetitions for the PUSCH.
 7. One or morenon-transitory computer-readable media (NTCRM) having instructions,stored thereon, that when executed by one or more processors of a nextgeneration Node B (gNB) cause the gNB to: encode, for transmission to auser equipment (UE), configuration information to configure repetitionsof a channel state information (CSI) report on a physical uplink sharedchannel (PUSCH), wherein the CSI report includes an aperiodic CSI(A-CSI) report or a semi-persistent CSI (SP-CSI) report; encode, fortransmission to the UE, a DCI to trigger the A-CSI report or activatethe SP-CSI report; and receive, from the UE on the PUSCH, the CSI reportwith repetitions based on the configuration information and the DCI. 8.The one or more NTCRM of claim 7, wherein the configuration informationindicates a number of the repetitions.
 9. The one or more NTCRM of claim8, wherein the number of repetitions is indicated separately from anumber of repetitions of the PUSCH.
 10. The one or more NTCRM of claim7, wherein the configuration information is transmitted via one or moreof minimum system information (MSI), remaining minimum systeminformation (RMSI), other system information (OSI), or dedicated radioresource control (RRC) signaling.
 11. The one or more NTCRM of claim 7,wherein the configuration information is configured per DCI format. 12.The one or more NTCRM of claim 7, wherein the CSI report is the A-CSIreport and is multiplexed on the PUSCH with a transport block, andwherein a number of the repetitions of the A-CSI is the same as a numberof repetitions for the PUSCH.
 13. One or more non-transitorycomputer-readable media (NTCRM) having instructions, stored thereon,that when executed by one or more processors of a user equipment (UE)cause the UE to: receive, from a gNodeB (gNB), configuration informationto indicate a repetition window for a physical random access channel(PRACH), wherein the repetition window includes a plurality of PRACHoccasions; and encode a PRACH message for transmission with repetitionin the respective PRACH occasions.
 14. The one or more NTCRM of claim13, wherein the configuration information indicates a starting positionand a number of PRACH repetitions.
 15. The one or more NTCRM of claim13, wherein the configuration information is received via one or more ofminimum system information (MSI), remaining minimum system information(RMSI), other system information (OSI), or dedicated radio resourcecontrol (RRC) signaling.
 16. The one or more NTCRM of claim 13, wherein,to indicate the repetition window, the configuration informationincludes an offset and a periodicity, wherein the offset is a slotoffset, a symbol offset, or a frame offset.
 17. The one or more NTCRM ofclaim 13, wherein the configuration information includes an indicationof whether the same beam or different beams are to be used for therepetitions of the PRACH message within the repetition window.
 18. Theone or more NTCRM of claim 13, wherein if the plurality of PRACHoccasions in the repetition window associated a same synchronizationsignal block (SSB) index are multiplexed in a frequency divisionmultiplexing (FDM) manner, the PRACH message is transmitted in only onePRACH occasion of the repetition window.
 19. The one or more NTCRM ofclaim 13, wherein the PRACH occasions for the repetitions are associatedwith a same synchronization signal block (SSB) for determination oftransmit power, path loss, and reference signal received power.
 20. Theone or more NTCRM of claim 13, wherein the PRACH occasions for therepetitions are associated with different synchronization signal blocks(SSBs) for determination of transmit power, path loss, and referencesignal received power.